Devin Martin committed 1a53207

Edited online

  • Participants
  • Parent commits d1b660e

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.
+# Check that your date is correct.  If the time is correct but the date is off the code will still be wrong.  Each 30 second increment that elapses is considered a new code window.  The same code isn't generated at the same time each day but rather a new code is generated every thirty seconds.
 # 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.
 === Clock Test ===