Skip to content

Conversation

@NHAS
Copy link

@NHAS NHAS commented Dec 20, 2020

An extension to #291, and (hopefully) full solution to #289

This change the random data generation to a cryptographically secure source and implements a repetition resistant nonce generation algorithm, which handles some edge cases where nonce reuse might occur.

This needs a bit of a look over to make sure its both backwards compatible and not missing anything.

NHAS added 4 commits December 20, 2020 21:59
This is so we can store the generated nonces to prevent reuse
An attacker would be able to cause the regeneration of nonces without verifying that the nonce was actually in use
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant