-
Notifications
You must be signed in to change notification settings - Fork 164
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
get rfc822Name/email from certificate's SAN? #72
Comments
There are two features here that I see:
I would expect that if one is doing S/MIME or similar then the first kind of API would be needed. I suspect that if somebody is implementing e.g. TLS client authentication then they might have a system that doesn't allow the first kind of API to be used and so the second kind of API is needed. Here's what I think would be required for this to be merged:
With good tests at each stage. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I don't see a way to get an email address out of a certificate's subject_alternate_name. Is that something that webpki could support? I think this is related to #64.
I have client certificates from which I want to get the email after verification is successful. Today I'm using openssl like this but I'm trying to avoid that dependency.
The text was updated successfully, but these errors were encountered: