database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-04-22 23:02:54 +03:00
Code

More forcefully recommend MD5 over crypt authentication.

Browse Source
This commit is contained in:
Bruce Momjian 2005-10-24 15:49:54 +00:00
parent 24fa8746ae
commit 42b689aed4
1 changed files with 10 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
doc/src/sgml/client-auth.sgml
View File

@ -1,5 +1,5 @@
<!-- <!--
$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.84 2005/10/24 15:38:36 momjian Exp $ $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.85 2005/10/24 15:49:54 momjian Exp $
--> -->
<chapter id="client-authentication"> <chapter id="client-authentication">
@ -319,11 +319,16 @@ hostnossl <replaceable>database</replaceable> <replaceable>user</replaceable>
<varlistentry> <varlistentry>
<term><literal>crypt</></term> <term><literal>crypt</></term>
<listitem> <listitem>
<note>
<para>
This option is recommended only for communicating with pre-7.2
clients.
</para>
</note>
<para> <para>
Require the client to supply a <function>crypt()</>-encrypted Require the client to supply a <function>crypt()</>-encrypted
password for authentication. password for authentication.
<literal>md5</literal> is preferred for 7.2 and later clients, <literal>md5</literal> is now recommended over <literal>crypt</>.
but pre-7.2 clients only support <literal>crypt</>.
See <xref linkend="auth-password"> for details. See <xref linkend="auth-password"> for details.
</para> </para>
</listitem> </listitem>
@ -589,8 +594,8 @@ local db1,db2,@demodbs all md5
<para> <para>
If you are at all concerned about password If you are at all concerned about password
<quote>sniffing</> attacks then <literal>md5</> is preferred, with <quote>sniffing</> attacks then <literal>md5</> is preferred, with
<literal>crypt</> a second choice if you must support pre-7.2 <literal>crypt</> to be used only if you must support pre-7.2
clients. Plain <literal>password</> should especially be avoided for clients. Plain <literal>password</> should be avoided especially for
connections over the open Internet (unless you use <acronym>SSL</acronym>, connections over the open Internet (unless you use <acronym>SSL</acronym>,
<acronym>SSH</>, or another <acronym>SSH</>, or another
communications security wrapper around the connection). communications security wrapper around the connection).