Use const time equality from byteable instead of crypto-api #697
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
|
Also, I think the only thing that still depends on crypto-api, tagged, cereal is skein. Depending on what people think of yesodweb/clientsession#23, skein is not strictly necessary as the aes-gcm or aes-ocb should be more mainstream/secure/fast. |
snoyberg
added a commit
that referenced
this pull request
Mar 18, 2014
Use const time equality from byteable instead of crypto-api
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.
Remove the need for crypto-api in yesod-form by using similar function from byteable (which is already a dependency, e.g. cryptohash depends on it).