mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-10-03 16:06:51 +02:00
It looks Ok, but it has one unnecessary step. There is no need to do the "mv
privkey.pem cert.pem.pw" if you just use "privkey.pem" in the following openssl command (e.g. openssl rsa -in privkey.pem -out cert.pem". But there is nothing wrong with it as it is now, as far as I can see. //Magnus
This commit is contained in:
parent
ab37224426
commit
87070ccc13
@ -1,5 +1,5 @@
|
|||||||
<!--
|
<!--
|
||||||
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.46 2001/01/08 21:01:54 petere Exp $
|
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.47 2001/01/24 15:19:36 momjian Exp $
|
||||||
-->
|
-->
|
||||||
|
|
||||||
<Chapter Id="runtime">
|
<Chapter Id="runtime">
|
||||||
@ -1911,8 +1911,7 @@ openssl req -new -text -out cert.req
|
|||||||
To remove the passphrase (as you must if you want automatic start-up of
|
To remove the passphrase (as you must if you want automatic start-up of
|
||||||
the postmaster), run the commands
|
the postmaster), run the commands
|
||||||
<programlisting>
|
<programlisting>
|
||||||
mv privkey.pem cert.pem.pw
|
openssl rsa -in privkey.pem -out cert.pem
|
||||||
openssl rsa -in cert.pem.pw -out cert.pem
|
|
||||||
</programlisting>
|
</programlisting>
|
||||||
Enter the old passphrase to unlock the existing key. Now do
|
Enter the old passphrase to unlock the existing key. Now do
|
||||||
<programlisting>
|
<programlisting>
|
||||||
|
Loading…
Reference in New Issue
Block a user