Dear all, I would like to discuss time drift issues in a hardware token, like the c200H3+, which sometimes has a slight time drift as reported by GOOZE users.
The c200H3+ has a time step size of 60 seconds.
Very rarely, time drift can be +-30 seconds.
To fix a time drift of +-30 seconds:
$ oathtool --totp CD22B780FFFD2D53696807ECD37F404DAE393270
--time-step-size=60 -w1 --now '30 seconds ago'
This output two results, giving a 120 seconds time frame.
To fix a time drift of +-1 minute:
$ oathtool --totp CD22B780FFFD2D53696807ECD37F404DAE393270
--time-step-size=60 -w2 --now '60 seconds ago'
This output three results, giving a 180 seconds time frame.
To fix a time drift of +-90 seconds:
$ oathtool --totp CD22B780FFFD2D53696807ECD37F404DAE393270
--time-step-size=60 -w3 --now '90 seconds ago'
This output four results, giving a 270 seconds time frame.
Any comments? Are these calculations correct?
Kind regards,
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
Signature valide (Jean-Michel Pouré <[email protected]>)
--
Jean-Michel Pouré - Gooze - http://www.gooze.eu
smime.p7s
Description: S/MIME cryptographic signature
