Add CRMF ProtocolEncrKeyControl support - #2443
Open
sfeng-c wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add support for the CRMF
protocolEncrKeycontrol defined in RFC 4211 Section 6.6.RFC 4211 defines
id-regCtrl-protocolEncrKeywith aSubjectPublicKeyInfoparameter, for use when the CA needs to encrypt information in a response to the requester.Reference:
https://www.rfc-editor.org/rfc/rfc4211.html#section-6.6
This change:
ProtocolEncrKeyControlbacked bySubjectPublicKeyInfo;CertificateRequestMessage.getControl()to recognizeid_regCtrl_protocolEncrKey;Tested with:
gradlew.bat :pkix:test --tests org.bouncycastle.cert.crmf.test.AllTestsAI assistance disclosure
OpenAI Codex was used to assist with the implementation and testing of this contribution. I reviewed and verified the resulting changes.