remove subject common name fallback support in CertVerifier
Categories
(Core :: Security: PSM, task, P2)
Tracking
()
People
(Reporter: keeler, Assigned: jschanck)
References
Details
(Whiteboard: [psm-backlog][psm-cleanup])
Attachments
(1 file)
Bug 1245280 and bug 1267463 began the process of deprecating fallback to subject common name matching against hostnames in TLS server certificate validation. However, certificates from imported roots were always exempt from this policy in Firefox. In the time since then, Chrome has deprecated fallback to the subject common name [0]. Chrome did have an enterprise policy option to re-enable this fallback, but it was removed in Chrome 66 [1].
[0] https://developers.google.com/web/updates/2017/03/chrome-58-deprecations#remove_support_for_commonname_matching_in_certificates
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=803791
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Updated•3 years ago
|
Comment 3•3 years ago
|
||
Backed out for causing failures at test_peerConnection_basicAudioNATRelayTLS.html.
Backout link: https://hg.mozilla.org/integration/autoland/rev/e5bcee1dfc4c2c0d8ce4c88156efb859df8cd86c
Failure log: https://treeherder.mozilla.org/logviewer?job_id=376046193&repo=autoland&lineNumber=6999
Assignee | ||
Comment 4•3 years ago
|
||
The failing test involves a self-signed certificate generated (at run time) by testing/tools/iceserver/iceserver.py
. That script fails to set a subject alternative name, so it is expected to fail w/o subject common name fallback support. I've updated the revision with a patch for iceserver.py
Comment 6•3 years ago
|
||
bugherder |
Assignee | ||
Comment 7•3 years ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: Validation of any manually installed certificates that lack the subjectAltName
extension will fail with error code SSL_ERROR_BAD_CERT_DOMAIN
.
[Affects Firefox for Android]: yes
[Suggested wording]: Removed "subject common name" fallback support from certificate validation. This fallback mode was previously enabled only for manually installed certificates. The CA Browser Forum Baseline Requirements have required the presence of the "subjectAltName" extension since 2012, and use of the subject common name was deprecated in RFC 2818.
[Links (documentation, blog post, etc)]:
Description
•