-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
reset() not working correctly #46
Comments
brycx
added a commit
that referenced
this issue
Dec 20, 2018
brycx
added a commit
that referenced
this issue
Dec 20, 2018
Fix #46: Reset the state even if it hasn't been finalized yet
In case of |
brycx
added a commit
that referenced
this issue
Dec 23, 2018
…heir init(), this adds tests to verify that the recent bug #46 is fixed on all init() input combinations
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently
reset()
checks whether or not the state is already finalized. If it is not finalized, it will not reset the state. So if someone were to callreset()
not having finalized the state before, incorrect results would be produced. Such streaming states includehmac
,poly1305
,blake2b
andcshake
.The text was updated successfully, but these errors were encountered: