From 4f6d275ac7c22f4dd8122e01864d64839860e315 Mon Sep 17 00:00:00 2001
From: Bruce Momjian <bruce@momjian.us>
Date: Thu, 21 Apr 2005 22:19:27 +0000
Subject: [PATCH] Clarify use of MD5 authentication and pg_shadow encryption.

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

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index 46daf06173..56d1454778 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.2 2005/01/28 22:38:50 tgl Exp $
+$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.70.4.3 2005/04/21 22:19:27 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>
 
-- 
2.50.1