Use libsodium and scrypt for hash_names #7
Merged
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.
This uses libsodium's scrypt implementation. It also returns the data frame with
stringsAsFactors=FALSE
. Plus I changed the doc slightly to emphasize that a secret, random salt should be used. Oh and the salt needs to be length=1 (i.e. one salt for all inputs).However the interface stays the same and I tried to leave the changes to a minimum.
Addresses #4 and #6
Downside/Upside: scrypt is about 40 times slower than sha1