postgres.git / summary / log / commit / refs

commit    0df4f75eeafa6d7c7ec9a42744f7acea3eff6383
Author:   Daniel Gustafsson <dgustafsson@postgresql.org>
Date:     Thu Feb 01 08:36:34 2024 +0000
First released in: 17.0, 14.11, 15.6, 16.2

    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 7fcddaa97df..740ae77b6d0 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -666,7 +666,7 @@ include_dir         <replaceable>directory</replaceable>
        format. To see the <literal>DN</literal> of a client certificate
        in this format, do
 <programlisting>
-openssl x509 -in myclient.crt -noout --subject -nameopt RFC2253 | sed "s/^subject=//"
+openssl x509 -in myclient.crt -noout -subject -nameopt RFC2253 | sed "s/^subject=//"
 </programlisting>
         Care needs to be taken when using this option, especially when using
         regular expression matching against the <literal>DN</literal>.


[parent: 781bc121de89]