summaryrefslogtreecommitdiff
path: root/lisp/emacs-lisp/lisp.el
diff options
context:
space:
mode:
authorJimmy Yuen Ho Wong <wyuenho@gmail.com>2018-07-13 06:18:55 +0100
committerJimmy Yuen Ho Wong <wyuenho@gmail.com>2018-07-14 17:50:46 +0100
commitfab6139b8954c4d33c4430a722337e09939aa777 (patch)
tree0d8b11f870f410622ebc792d7201526596049838 /lisp/emacs-lisp/lisp.el
parent87484dc27ec7a6e708c7e0ceaf96bff1ee064174 (diff)
downloademacs-fab6139b8954c4d33c4430a722337e09939aa777.tar.gz
emacs-fab6139b8954c4d33c4430a722337e09939aa777.tar.bz2
emacs-fab6139b8954c4d33c4430a722337e09939aa777.zip
Show full issuer and subject distinguished names
CAs like Let's Encrypt do not put O and OU into the Subject's DN. Similarly, O and OU are often used to indicate Domain Validated or Organization Validation as opposed to the actual OU. Issuer CN often contains the issuer's server or as an indication of Extended Validation certificate as opposed to the actual issuer organization. The Hostname part as extracted from the Subject is also confusing, as in the case of a hostname mismatch, the Subject's CN, which `nsm-format-certificate' naively calls the Hostname, will not actually match the hostname in the problem preamble. * lisp/net/nsm.el (nsm-format-certificate): Show full DN of Issuer and Subject. Remove Hostname. (nsm-certificate-part, nsm-parse-subject): Removed.
Diffstat (limited to 'lisp/emacs-lisp/lisp.el')
0 files changed, 0 insertions, 0 deletions