From 61b1991ad0912ab4fbf9616f868a594a53f7d9fc Mon Sep 17 00:00:00 2001 From: Daniel Gustafsson Date: Thu, 1 Feb 2024 09:36:34 +0100 Subject: [PATCH] doc: Fix incorrect openssl option The openssl command for displaying the DN of a client certificate was using --subject and not the single-dash option -subject. While recent versions of openssl handles double dash options, earlier does not so fix by using just -subject (which is per the openssl documentation). Backpatch to v14 where this was introduced. Reported-by: konkove@gmail.com Discussion: https://postgr.es/m/170672168899.666.10442618407194498217@wrigleys.postgresql.org Backpatch-through: v14 --- doc/src/sgml/client-auth.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index 44f8fd02b0..84d041a9ad 100644 --- a/doc/src/sgml/client-auth.sgml +++ b/doc/src/sgml/client-auth.sgml @@ -631,7 +631,7 @@ hostnogssenc database userDN of a client certificate in this format, do -openssl x509 -in myclient.crt -noout --subject -nameopt RFC2253 | sed "s/^subject=//" +openssl x509 -in myclient.crt -noout -subject -nameopt RFC2253 | sed "s/^subject=//" Care needs to be taken when using this option, especially when using regular expression matching against the DN.