-
-
Notifications
You must be signed in to change notification settings - Fork 746
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
support SubjectAlternativeName::other_name again #1911
Comments
Thanks for reporting this! I think the right API here is probably to add an
`other_name2` (better names welcome!) method to SAN, which takes an
`OtherName` object, which has two fields, the OID and the DER contents. Are
you interested in working on this and sending a PR?
…On Thu, Apr 27, 2023 at 4:24 PM huettner94 ***@***.***> wrote:
As written here
<482575b#diff-3105f7585b1063b001e5ff3f482774ddf31242e7390eb0f9b61fbd145754f223R544-R550>
i'm opening this issue as i' m using SubjectAlternativeName::other_name.
I'm using it to generate a certificate for a testroutine for RFC 9174
<https://datatracker.ietf.org/doc/rfc9174/> which defines the SAN of the
certificate should be in other_name 1.3.6.1.5.5.7.8.11 (Appendix C).
The code for this test can be found here
<https://github.com/huettner94/dtn/blob/d32800b74504da462da40fc1bde029caa8a37739/tcpcl/tests/common/tls.rs#L24-L27>
.
For now i'm using the following alternative, but it looks like it is
deprecated:
let subject_alternative_name = X509Extension::new_nid(
None,
Some(&builder.x509v3_context(None, None)),
Nid::SUBJECT_ALT_NAME,
&format!("otherName:1.3.6.1.5.5.7.8.11;IA5STRING:{}", sanname),
)
.unwrap();
Thank you for your help
—
Reply to this email directly, view it on GitHub
<#1911>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAAGBDQCTOFG3A65NBVRQTXDLIYJANCNFSM6AAAAAAXOLHCIM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
All that is necessary for evil to succeed is for good people to do nothing.
|
Thanks for the hint. I will try |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As written here i'm opening this issue as i' m using
SubjectAlternativeName::other_name
.I'm using it to generate a certificate for a testroutine for RFC 9174 which defines the SAN of the certificate should be in other_name
1.3.6.1.5.5.7.8.11
(Appendix C).The code for this test can be found here.
For now i'm using the following alternative, but it looks like it is deprecated:
Thank you for your help
The text was updated successfully, but these errors were encountered: