|
1 | | -<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.105 2007/12/29 04:15:38 momjian Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.106 2008/01/05 13:17:00 petere Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="client-authentication"> |
4 | 4 | <title>Client Authentication</title> |
@@ -666,10 +666,10 @@ local db1,db2,@demodbs all md5 |
666 | 666 |
|
667 | 667 | <para> |
668 | 668 | <productname>GSSAPI</productname> is an industry-standard protocol |
669 | | - for secure authentication defined inRFC2743. |
| 669 | + for secure authentication defined inRFC 2743. |
670 | 670 | <productname>PostgreSQL</productname> supports |
671 | 671 | <productname>GSSAPI</productname> with <productname>Kerberos</productname> |
672 | | - authentication according toRFC1964. <productname>GSSAPI</productname> |
| 672 | + authentication according toRFC 1964. <productname>GSSAPI</productname> |
673 | 673 | provides automatic authentication (single sign-on) for systems |
674 | 674 | that support it. The authentication itself is secure, but the |
675 | 675 | data sent over the connection will be in clear unless |
@@ -851,7 +851,7 @@ local db1,db2,@demodbs all md5 |
851 | 851 |
|
852 | 852 | <para> |
853 | 853 | The <quote>Identification Protocol</quote> is described in |
854 | | -<citetitle>RFC 1413</citetitle>. Virtually every Unix-like |
| 854 | + RFC 1413. Virtually every Unix-like |
855 | 855 | operating system ships with an ident server that listens on TCP |
856 | 856 | port 113 by default. The basic functionality of an ident server |
857 | 857 | is to answer questions like <quote>What user initiated the |
|