Add -key-encipherment-selector
and use CA certs for verification
#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.
When a SCEP server returns multiple certificates, it is possible that not all certificates can or should be used for encryption. There already was a
KeyEnciphermentsSelector
, but that wasn't readily usable with the provided SCEP client. A new flag was added to enable this selector:-key-encipherment-selector
. It will filter out certificates that aren't marked as being usable for key or data encryption.When verifying the
PKIMessage
from the CA only theRecipients
in the outgoing message were being looked through when selecting a certificate to verify the signature. This commit changes that by including all certificates returned by the CA when the client performs theGetCACerts
operation.