|author||Robin Krahl <firstname.lastname@example.org>||2019-01-25 19:19:36 +0000|
|committer||Robin Krahl <email@example.com>||2019-01-25 20:22:28 +0100|
Add tolerance for timing issues to the TOTP tests
The TOTP test with the timestamp 59 often fails as the Nitrokey’s clock ticks between setting the time and generating the TOTP code. This patch also allows the TOTP code for timestamp 60 for this test case.
Diffstat (limited to 'README.md')
1 files changed, 0 insertions, 2 deletions
@@ -60,8 +60,6 @@ an AES key has been built. Some tests will overwrite the data stored on the
Nitrokey device or perform a factory reset. Never execute the tests if you
unless yout want to destroy all data on all connected Nitrokey devices!
-The `totp_no_pin` and `totp_pin` tests can occasionally fail due to bad timing.
Thanks to Nitrokey UG for providing a Nitrokey Storage to support the