Skip to content

Commit 26bb65d

Browse files
committed
Clarify that only crypt can't use md5 pg_shadow passwords.
1 parent c82b895 commit 26bb65d

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

doc/src/sgml/client-auth.sgml

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.75 2005/04/21 22:19:19 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.76 2005/04/22 04:18:58 momjian Exp $
33
-->
44

55
<chapter id="client-authentication">
@@ -575,9 +575,8 @@ local db1,db2,@demodbs all md5
575575
The password-based authentication methods are <literal>md5</>,
576576
<literal>crypt</>, and <literal>password</>. These methods operate
577577
similarly except for the way that the password is sent across the
578-
connection. However, only <literal>md5</> allows encrypted
579-
passwords to be stored in <structname>pg_shadow</structname>;
580-
the other two require unencrypted passwords to be stored there.
578+
connection. However, <literal>crypt</> does not allow encrypted
579+
passwords to be stored in <structname>pg_shadow</structname>.
581580
</para>
582581

583582
<para>

0 commit comments

Comments
 (0)
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy