Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit87070cc

Browse files
committed
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 followingopenssl 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
1 parentab37224 commit87070cc

File tree

1 file changed

+2
-3
lines changed

1 file changed

+2
-3
lines changed

‎doc/src/sgml/runtime.sgml

Lines changed: 2 additions & 3 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.46 2001/01/08 21:01:54 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/runtime.sgml,v 1.47 2001/01/24 15:19:36 momjian Exp $
33
-->
44

55
<Chapter Id="runtime">
@@ -1911,8 +1911,7 @@ openssl req -new -text -out cert.req
19111911
To remove the passphrase (as you must if you want automatic start-up of
19121912
the postmaster), run the commands
19131913
<programlisting>
1914-
mv privkey.pem cert.pem.pw
1915-
openssl rsa -in cert.pem.pw -out cert.pem
1914+
openssl rsa -in privkey.pem -out cert.pem
19161915
</programlisting>
19171916
Enter the old passphrase to unlock the existing key. Now do
19181917
<programlisting>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp