-
Notifications
You must be signed in to change notification settings - Fork 51
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
Address further IP address support feedback #24
Conversation
Use `EndEntityCert::verify_is_valid_for_subject_name` that accepts a `SubjectNameRef` as the subject name to match the certificate against.
9eff60d
to
d7c9629
Compare
59c46b8
to
8afa5cc
Compare
src/subject_name/mod.rs
Outdated
|
||
mod verify; | ||
pub(super) use verify::{check_name_constraints, verify_cert_dns_name, verify_cert_subject_name}; | ||
pub use verify::{check_name_constraints, verify_cert_subject_name}; |
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.
But then this change doesn't make much sense? We don't want to make these free functions part of the public API, right, so they should have limited visibility? (Hopefully we can merge #22 soon.) If pub(super)
is not enough they should probably become pub(crate)
.
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, updated. pub(super)
did fit the bill.
8afa5cc
to
18f86ff
Compare
Merged with a fixup (e69b9df) |
name
tosubject_name
EndEntityCert::verify_is_valid_for_dns_name
Addresses further feedback provided in #5