FreeNAS created certificates broken by Chrome 58 and others (per RFC 2818)

[agrajag9]

Chrome 58 is currently rolling out and Google has made the decision to start ignoring the Common Name field in X509 certificates, relying instead entirely on the Subject Alternative Name field. This means that any certificates generated from the FreeNAS 9.10 WebUI will be unrecognized.

https://tools.ietf.org/html/rfc2818

https://groups.google.com/a/chromium.org/forum/#!msg/security-dev/IGT2fLJrAeo/csf_1Rh1AwAJ

http://unmitigatedrisk.com/?p=381

This should be a fairly simple fix in terms of the back-end openssl command.

 

[dlavigne]

Please create a feature request at bugs.freenas.org and post the issue number here.

 

[agrajag9]

https://bugs.freenas.org/issues/23502