diff options
author | Bruce Momjian <bruce@momjian.us> | 2005-04-22 04:19:02 +0000 |
---|---|---|
committer | Bruce Momjian <bruce@momjian.us> | 2005-04-22 04:19:02 +0000 |
commit | ddae2b6801b23765a0e73c0ddbb4f97f65d5e6f2 (patch) | |
tree | a9680b50292d7b6fb53cb0ef34081d0feb2059f9 | |
parent | 4f6d275ac7c22f4dd8122e01864d64839860e315 (diff) |
Clarify that only crypt can't use md5 pg_shadow passwords.
-rw-r--r-- | doc/src/sgml/client-auth.sgml | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index 56d1454778b..062fa371b8a 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.70.4.3 2005/04/21 22:19:27 momjian Exp $ +$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.70.4.4 2005/04/22 04:19:02 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> |