Singular KeyDerivationStringDataParams #165
Open
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
|
@miekg I would be happy to help work on updating the go version and also merge in your changes with mine here |
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.
Implement PKCS #11 CK_KEY_DERIVATION_STRING_DATA.
Unit tests cover AES Key Derivation
Discussion
This PR ended up being a case of convergent evolution with #123 KeyDerivationStringDataParams but follows the current convention (and uses putKeyDerivationStringDataParams() where PR 123 does not).
I would be happy to revise this PR and merge changes with #123 but that has not been merged yet.