Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • 5
    "Usage of common name only is not seen as secure enough." - It is not a security issue but simply that use of CN was declared obsolete for ages. Commented Nov 1, 2017 at 10:49
  • You using a private PKI? Public ones have used the SAN for ages. Commented Nov 1, 2017 at 10:54
  • Yes, private PKI. We are in the process of updating the internally used procedures, practices, etc.. Commented Nov 1, 2017 at 10:56
  • 1
    Related: Thread for Chrome: 2017-01-28, Chromium security-dev forum, Ryan Sleevi, Intent to Remove: Support for commonName matching in certificates (Related Firefox/Mozilla Bug 1245280 is linked to from there.) Commented Nov 1, 2017 at 14:10
  • 1
    I'm voting to close this question as off-topic because only the internal dev teams of these products can speak to their development roadmaps. Commented Nov 2, 2017 at 14:42