Vendor defined mechanism in MechanismWithParam #217
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.
Hello,
This pull request introduces minimal changes required for supporting GOSTR mechanisms within the library.
There is a document describing all GOSTR mechanisms. There is a lot of overlap in the NIST implementation, but to ensure compatibility, the constants are chosen from the vendor-defined range (0x80000000 | 0x54321xxx).
I did not add new constants for the GOSTR parameter, but added a check in the MechanismWithParam class for the vendor-defined mechanism and to interpret the mechanism parameters as a set of bytes if the mechanism parameters are used.
The implementation has been successfully tested against two different vendor PKCS#11 libraries supporting GOST algorithms, specifically verifying data signing functionality.
These changes are backward-compatible and do not affect the existing operation of non-vendor-defined mechanisms.