Finish creating SymmetricKeys from byte arrays #262
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.
In the course of #259, I wanted to finish creating a
PK11SymKey
from a byte array. In doing so, I realized that, when we specify aSecretKeySpec
, we do the import correctly already in ourSecretKeyFactory
implementation,JSSSecretKeyFactorySpi
. However, what is missing is support for a few newer HMAC variants.This PR does the following things:
SymmetricKey.Usage
toPKCS11Constants
values. This is currently unused, but could be used in the future.SymmetricKey.Types
... mostly for HMAC. Otherwise, you'd pass one name toSecretKeyFactory
and another toSecretKeySpec
.