Welcome! Log In Create A New Profile

Advanced

SSL Alternative Subject Name validation

Bart Warmerdam
August 04, 2016 11:08AM
Hello,

According to src/event/ngx_event_openssl.c (line ~ 3094)

/*
* As per RFC6125 and RFC2818, we check subjectAltName extension,
* and if it's not present - commonName in Subject is checked.
*/


But according to the https://tools.ietf.org/html/rfc6125 the validation
this case is more restrictive:

0 If a subjectAltName extension of type dNSName is present in the
certificate, it SHOULD be used as the source of the server's
identity.

This means that if e.g. an email address (GEN_EMAIL) is part of the
subjectAltName, and no DNSName is present, the CN name is never checked
in this case. I'd expect the CN to be checked in this case. The jump to
the failed label should only be done if there was at least one DNSName.
Do you share this view and do you accept a patch for this?

Regards,

B.

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

SSL Alternative Subject Name validation

Bart Warmerdam 691 August 04, 2016 11:08AM

Re: SSL Alternative Subject Name validation

Maxim Dounin 325 August 06, 2016 09:32AM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 235
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready