Devin Martin committed 25a2a94

Edited online

Comments (0)

Files changed (1)

 # Check that your system time is correct.  If your computer supports auto setting of the clock based on a network time server than this is a good way to ensure that everything correct.
 # Check your timezone and daylight savings settings.  These codes are generated using UTC.  If your timezone setting is off but your time is correct for the local time then your UTC time will be off by as many hours as your timezone is off.  The codes generated in this case will be completely incorrect.
 # Be sure that the verifying system uses UTC to generate codes.  The RFC that defines the TOTP standard used here recommends UTC but that doesn't mean that the verifying system uses UTC.  If they don't use UTC then KeeOtp will not work since KeeOtp always uses UTC.  There is a feature request to add this capability in a future version.  See issue #8 to follow this request.
+== Key ==
+KeeOtp currently accepts keys as base32.  Ensure that the key provided to you is correctly encoded as base32.  The known systems that KeeOtp works with all provide the key as base32 already so no additional encoding should be needed.  The spaces provided in those keys will need to be stripped out before entering the key.
+It is possible however that the system provides the key in some other way.  If this is the case you will need to convert it to base32 as that is currently the only way that KeeOtp accepts keys.  There is a feature request for alternate encodings.  See #7 to follow that request.
+# Ensure that the key is encoded correctly.  Look up the key encoding used by the service.  Google, Amazon, and Dropbox all use base32 to no additional encoding is needed.  The spaces will need to be stripped out.
+# If your key is encoded using base64 or hex you will need to translate that to base32.