mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Document problem with NULL SSL ciphers and man-in-the-middle attacks.

Browse Source
This commit is contained in:
Bruce Momjian 2007-12-29 03:36:56 +00:00
parent f5678e8e07
commit 400be4ef98
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
doc/src/sgml/runtime.sgml
View File

@ -1,4 +1,4 @@
<!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.397 2007/12/25 17:06:52 momjian Exp $ --> <!-- $PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.398 2007/12/29 03:36:56 momjian Exp $ -->
<chapter Id="runtime"> <chapter Id="runtime">
<title>Operating System Environment</title> <title>Operating System Environment</title>
@ -1604,7 +1604,10 @@ $ <userinput>kill -INT `head -1 /usr/local/pgsql/data/postmaster.pid`</userinput
ciphers can be specified in the <productname>OpenSSL</productname> ciphers can be specified in the <productname>OpenSSL</productname>
configuration file, you can specify ciphers specifically for use by configuration file, you can specify ciphers specifically for use by
the database server by modifying <xref linkend="guc-ssl-ciphers"> in the database server by modifying <xref linkend="guc-ssl-ciphers"> in
<filename>postgresql.conf</>. <filename>postgresql.conf</>. It is possible to allow authentication
without the overhead of encryption by using <literal>NULL-SHA</> or
<literal>NULL-MD5</> ciphers. However, a man-in-the-middle could read
and pass communications between client and server.
</para> </para>
<para> <para>