-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add PreSpecified(Vec<u8>) option to KeyIdMethod. #197
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks great, just one nit and a request for a test from me.
6c2f542
to
5b81bde
Compare
I've implemented all feedback and all tests are green :) Thanks for helping me with resolving this issue and reviewing this pull-request. Your feedback was really helpful and I learned a few new things! Once merged, would it be possible to push a new release containing this fix? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! LGTM mod my one suggestion for removing the duplication of the expected SKI in the test.
5b81bde
to
6b784a1
Compare
If using from_ca_cert_der/_pem, the key_identifier_method would always be set to Sha256, which is not always true. If using OpenSSL for example SHA1 would be used. If the provided CA certificate contains a SubjectKeyIdentifier extension, then this option will be automatically set. Fixes rustls#195.
6b784a1
to
b14393e
Compare
I updated the branch to address my tiny review nit and to rebase on main. |
If using from_ca_cert_der/_pem, the key_identifier_method would always be set to Sha256, which is not always true. If using OpenSSL for example SHA1 would be used.
If the provided CA certificate contains a SubjectKeyIdentifier extension, then this option will be automatically set.
Fixes #195.