pkcs11-tool: let -m accept hexadecimal strings, e.g., 0x80001234 #1302
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
|
When we list mechanisms we output |
aalba6675
changed the title
|
PR updated(and squashed), per @dengert comment #1301 (comment) |
|
Please also update |
To support vendor mechanisms, let -m accept hexadecimal strings, e.g., -m 0x80001234
|
Updated |
|
thanks! |
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.
Checklist
Fixes #1301: convert user specified mechanisms
-m mechtype-0xNNNNNNNNto UL (CK_MECHANISM_TYPE).To work with vendor HSMs that require proprietary mechanisms such as AWS CloudHSM in FIPS-mode which uses
0x800001420x80000143for RSA keypairgen instead of the pkcs11-tool defaults ofCKM_RSA_PKCS_KEY_PAIR_GEN,CKM_RSA_X9_31_KEY_PAIR_GEN[UPDATE] remove
mechtype-as prefix, specify mechanism-in-hex as-m 0x80001234for example[UPDATE] updated XML documentation