|
1 | | -<!-- $Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.24 2001/11/08 23:36:18 petere Exp $ --> |
| 1 | +<!-- $Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.25 2001/11/12 02:35:16 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="client-authentication"> |
4 | 4 | <title>Client Authentication</title> |
@@ -236,13 +236,12 @@ hostssl <replaceable>database</replaceable> <replaceable>IP-address</replaceable |
236 | 236 | <listitem> |
237 | 237 | <para> |
238 | 238 | Like the <literal>md5</literal> method but uses older crypt |
239 | | - authentication for pre-7.2 clients. <literal>md5</literal> |
240 | | - is preferred, unless you need to support old clients that |
241 | | - do not have <literal>md5</literal>. The <literal>crypt</> |
242 | | - method is not compatible with encrypting passwords in |
243 | | - <filename>pg_shadow</>, and it has been observed to fail |
244 | | - when client and server machines have different implementations |
245 | | - of the crypt() library routine. |
| 239 | + authentication for pre-7.2 clients. <literal>md5</literal> is |
| 240 | + preferred for 7.2 and later clients. The <literal>crypt</> |
| 241 | + method is also not compatible with encrypting passwords in |
| 242 | + <filename>pg_shadow</>, and may fail if client and server |
| 243 | + machines have different implementations of the crypt() library |
| 244 | + routine. |
246 | 245 | </para> |
247 | 246 | </listitem> |
248 | 247 | </varlistentry> |
|