This patch improves the "Client Authentication" section of the user's

guide in a few minor ways.

Neil Conway

diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml
index b6f49b958489ced0ab7aa387251a168a6d43dabd..1cc48a65379221955faf0b3ea3b77b67fac30bf6 100644 (file)
--- a/doc/src/sgml/client-auth.sgml
+++ b/doc/src/sgml/client-auth.sgml
@@ -1,5 +1,5 @@
 
 
 
@@ -29,8 +29,9 @@ $Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.35 2002/04/09 00:38:24
 
  
   PostgreSQL offers a number of different
-  client authentication methods. The method to be used can be selected
-  on the basis of (client) host, database, and user.
+  client authentication methods. The method used to authenticate a
+  particular client connection can be selected on the basis of
+  (client) host address, database, and user.
  
 
  
@@ -56,8 +57,8 @@ $Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.35 2002/04/09 00:38:24
    pg_hba.conf in the data directory, e.g.,
    /usr/local/pgsql/data/pg_hba.conf.
    (HBA stands for host-based authentication.) A default
-   pg_hba.conf file is installed when the data area
-   is initialized by initdb.
+   pg_hba.conf file is installed when the data
+   directory is initialized by initdb.
   
 
   
@@ -124,7 +125,7 @@ hostssl database user 
        enabled with the -l option or equivalent configuration
        setting when the server is started.  (Note: host
        records will match either SSL or non-SSL connection attempts, but
-       hostssl records requires SSL connections.)
+       hostssl records require SSL connections.)
       
      
     
@@ -199,9 +200,11 @@ hostssl database user 
          trust
          
          
-          The connection is allowed unconditionally. This method allows
-          any user that has login access to the client host to connect as
-          any PostgreSQL user whatsoever.
+          The connection is allowed unconditionally. This method
+          allows anyone that can connect to the
+          PostgreSQL database to login as
+          any PostgreSQL user they like,
+          without the need for a password.
          
         
        
@@ -222,7 +225,7 @@ hostssl database user 
          
           Requires the client to supply an MD5 encrypted password for
           authentication. This is the only method that allows encrypted
-          passwords to be stored in pg_shadow.
+          passwords to be stored in pg_shadow.
          
         
        
@@ -273,15 +276,17 @@ hostssl database user 
         
     
           For TCP/IP connections, authentication is done by contacting
-          the ident server on the client host.
-          This is only as secure as the client machine. You must specify
-          the map name after the 'ident' keyword. It determines how to
-          map remote user names to PostgreSQL user names. If you use
+          the ident server on the client
+          host. This is only as secure as the client machine. You must
+          specify the map name after the 'ident' keyword. It
+          determines how to map remote user names to
+          PostgreSQL user names. If you use
           "sameuser", the user names are assumed to be identical. If
           not, the map name is looked up in the $PGDATA/pg_ident.conf
           file. The connection is accepted if that file contains an
-          entry for this map name with the ident-supplied user name and
-          the requested PostgreSQL user name.
+          entry for this map name with the ident-supplied user name
+          and the requested PostgreSQL user
+          name.
          
          
           On machines that support unix-domain socket credentials
@@ -317,8 +322,8 @@ hostssl database user 
           postgresql. You can optionally supply you
           own service name after the pam keyword in the
           file. For more information about PAM, please read the 
-          url="http://www.kernel.org/pub/linux/libs/pam/">L
-          inux-PAM Page and the 
+          url="http://www.kernel.org/pub/linux/libs/pam/">Linux-PAM
+          Page and the 
           url="http://www.sun.com/software/solaris/pam/">
           class="osname">Solaris PAM Page.
          




This is the main PostgreSQL git repository.
RSS
Atom



window.onload = function () {
	var tz_cookie = { name: 'gitweb_tz', expires: 14, path: '/' };
	onloadTZSetup('local', tz_cookie, 'datetime');
};