scrypt: allow hash.Hash payload, similar to hkdf & pbkdf2 #244
+8
−2
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.
Allow to adapt payload type & complexity via hash.Hash Interface, similar to all other golang.org/x/crypto KDF functions (hkdf, pbkdf2,...).
This would allow to continue to use and apapt existing scrypt based implementations in 2023+, ignoring the increased (cheap) availibility of sha2 hardware assisted solutions.