postgres.git / summary / log / commit / refs

commit    26bb65df1e76e88bf0915cc563a627f983bc9ee1
Author:   Bruce Momjian <bruce@momjian.us>
Date:     Fri Apr 22 04:18:58 2005 +0000
First released in: 8.1.0, 8.0.3

    Clarify that only crypt can't use md5 pg_shadow passwords.


 doc/src/sgml/client-auth.sgml | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 872fbebe61c..18269067f84 100644
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1,5 +1,5 @@
 <!--
-$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.75 2005/04/21 22:19:19 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.76 2005/04/22 04:18:58 momjian Exp $
 -->
 
 <chapter id="client-authentication">
@@ -575,9 +575,8 @@ local   db1,db2,@demodbs  all                         md5
     The password-based authentication methods are <literal>md5</>,
     <literal>crypt</>, and <literal>password</>. These methods operate
     similarly except for the way that the password is sent across the
-    connection.  However, only <literal>md5</> allows encrypted
-    passwords to be stored in <structname>pg_shadow</structname>;
-    the other two require unencrypted passwords to be stored there.
+    connection.  However, <literal>crypt</> does not allow encrypted
+    passwords to be stored in <structname>pg_shadow</structname>.
    </para>
 
    <para>


[parent: c82b8952845e]