You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 6, 2021. It is now read-only.
Thomas Habets edited this page Nov 23, 2016
·
5 revisions
The vast majority of problems with TOTP two-step verification are a
direct result of the server and the token-generator having different
ideas of what the current time is. Some amount of time skew is tolerated.
But significant differences will usually result in two-step verification failing.
The PAM module has an optional feature to detect and compensate for
excessive skew in time stamps. If enabled, if requires the user to
repeatedly try to log in. After a sequence of three successful tokens
the PAM module learns the client's time skew and will subsequently
compensate for it. See the README file for details.
But sometimes interactive debugging tools are more helpful in tracking
down problems. For this purpose, you can use the interactive
TOTP debugger. And you can also run the demo.c program to see if your token would be accepted by the server.