add otp operation about former #24
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
April 14, 2016 00:25
|
How is this different from the window kwarg to verify? |
|
OK, I see now how it's different - you want the user to submit two subsequent TOTPs. I think that's an antipattern. One should just have the user submit one TOTP, verify against a window of one or more timesteps, and adaptively adjust the clock skew correction if desired. If you can point me to a discussion/opinion on this, I can be persuaded otherwise. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Many websites verify current otp code and former otp code,which can make user input otp code when time end up soon.So,i add former function and verify_former function to make then operation more convenient.