Skip to content

Commit 2905a2c

Browse files
committed
>openssl req -new -text -out cert.req (you will have to enter a password)
>mv privkey.pem cert.pem.pw >openssl rsa -in cert.pem.pw -out cert.pem (this removes the password) >openssl req -x509 -in cert.req -text -key cert.pem -out cert.cert then cp cert.pem $PGDATA/server.key cp cert.cert $PGDATA/server.crt Thank you; this works. Oliver Elphick
1 parent 1db9cce commit 2905a2c

File tree

1 file changed

+24
-19
lines changed

1 file changed

+24
-19
lines changed

doc/src/sgml/runtime.sgml

Lines changed: 24 additions & 19 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.42 2000/12/17 11:22:00 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.43 2000/12/21 19:08:05 momjian Exp $
33
-->
44

55
<Chapter Id="runtime">
@@ -1823,26 +1823,31 @@ set semsys:seminfo_semmsl=32
18231823
<para>
18241824
For details on how to create your server private key and certificate,
18251825
refer to the <productname>OpenSSL</> documentation. A simple self-signed
1826-
certificate can be used to get started testing, but a certificate signed
1826+
certificate can be used to get started for testing, but a certificate signed
18271827
by a CA (either one of the global CAs or a local one) should be used in
18281828
production so the client can verify the servers identity. To create
1829-
a quick self-signed certificate, use the <filename>CA.pl</filename>
1830-
script included in OpenSSL:
1831-
<programlisting>
1832-
CA.pl -newcert
1833-
</programlisting>
1834-
Fill out the information the script asks for. Make sure to enter
1835-
the local host name as Common Name. The script will generate a key
1836-
that is passphrase protected. To remove the passphrase (required
1837-
if you want automatic start-up of the postmaster), run the command
1838-
<programlisting>
1839-
openssl x509 -inform PEM -outform PEM -in newreq.pem -out newkey_no_passphrase.pem
1840-
</programlisting>
1841-
Enter the old passphrase to unlock the existing key. Copy the file
1842-
<filename>newreq.pem</> to <filename><replaceable>PGDATA</>/server.crt</>
1843-
and <filename>newkey_no_passphrase.pem</> to
1844-
<filename><replaceable>PGDATA</>/server.key</>. Remove the PRIVATE KEY part
1845-
from the <filename>server.crt</filename> using any text editor.
1829+
a quick self-signed certificate, use the following OpenSSL command:
1830+
<programlisting>
1831+
openssl req -new -text -out cert.req
1832+
</programlisting>
1833+
Fill out the information that openssl asks for. Make sure that you enter
1834+
the local host name as Common Name; the challenge password can be
1835+
left blank. The script will generate a key that is passphrase protected;
1836+
it will not accept a pass phrase that is less than four characters long.
1837+
To remove the passphrase (as you must if you want automatic start-up of
1838+
the postmaster), run the commands
1839+
<programlisting>
1840+
mv privkey.pem cert.pem.pw
1841+
openssl rsa -in cert.pem.pw -out cert.pem
1842+
</programlisting>
1843+
Enter the old passphrase to unlock the existing key. Now do
1844+
</programlisting>
1845+
openssl req -x509 -in cert.req -text -key cert.pem -out cert.cert
1846+
cp cert.pem $PGDATA/server.key
1847+
cp cert.cert $PGDATA/server.crt
1848+
</programlisting>
1849+
to turn the certificate into a self-signed certificate and to copy the
1850+
key and certificate to where the postmaster will look for them.
18461851
</para>
18471852
</sect1>
18481853

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy