aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2005-04-21 22:19:19 +0000
committerBruce Momjian <bruce@momjian.us>2005-04-21 22:19:19 +0000
commitc82b8952845ed43599927b9aaf189b2156941435 (patch)
treeda716d6fa9b75ff5b7d6560ae4bdcb28165ae2c9
parent14c7fba3f7d0769d8a063dea2854693f35535f6a (diff)
downloadpostgresql-c82b8952845ed43599927b9aaf189b2156941435.tar.gz
postgresql-c82b8952845ed43599927b9aaf189b2156941435.zip
Clarify use of MD5 authentication and pg_shadow encryption.
-rw-r--r--doc/src/sgml/client-auth.sgml6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index f7c36bfb91c..872fbebe61c 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.74 2005/04/09 03:52:43 momjian Exp $
+$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.75 2005/04/21 22:19:19 momjian Exp $
-->
<chapter id="client-authentication">
@@ -575,8 +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. But only <literal>md5</> supports encrypted
- passwords stored in <structname>pg_shadow</structname>;
+ 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.
</para>