1
1
<!--
2
- $Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.43 2003/01/06 03:18:26 momjian Exp $
2
+ $Header: /cvsroot/pgsql/doc/src/sgml/client-auth.sgml,v 1.44 2003/01/19 00:13:28 momjian Exp $
3
3
-->
4
4
5
5
<chapter id="client-authentication">
@@ -110,8 +110,7 @@ hostssl <replaceable>database</replaceable> <replaceable>user</replaceable> <
110
110
This record matches connection attempts using TCP/IP networks.
111
111
Note that TCP/IP connections are disabled unless the server is
112
112
started with the <option>-i</option> option or the
113
- <literal>tcpip_socket</> <filename>postgresql.conf</>
114
- configuration parameter is enabled.
113
+ <varname>tcpip_socket</> configuration parameter is enabled.
115
114
</para>
116
115
</listitem>
117
116
</varlistentry>
@@ -129,9 +128,8 @@ hostssl <replaceable>database</replaceable> <replaceable>user</replaceable> <
129
128
<para>
130
129
To be able make use of this option the server must be built
131
130
with SSL support enabled. Furthermore, SSL must be enabled by
132
- enabling the option <literal>ssl</literal> in
133
- <filename>postgresql.conf</filename> (see <xref
134
- linkend="runtime-config">).
131
+ enabling the <varname>ssl</varname> configuration parameter
132
+ (see <xref linkend="runtime-config"> for more information).
135
133
</para>
136
134
</listitem>
137
135
</varlistentry>
@@ -191,8 +189,8 @@ hostssl <replaceable>database</replaceable> <replaceable>user</replaceable> <
191
189
must be zero for the record to match. (Of course IP addresses
192
190
can be spoofed but this consideration is beyond the scope of
193
191
<productname>PostgreSQL</productname>.) If you machine supports
194
- IPv6, the default <filename>pg_hba.conf</> will have an IPv6
195
- entry for <literal>localhost</>. You can add your own IPv6
192
+ IPv6, the default <filename>pg_hba.conf</> file will have an
193
+ IPv6 entry for <literal>localhost</>. You can add your own IPv6
196
194
entries to the file. IPv6 entries are used only for IPv6
197
195
connections.
198
196
</para>
@@ -486,17 +484,18 @@ local db1,db2,@demodbs all md5
486
484
</para>
487
485
488
486
<para>
489
- <literal>trust</> authentication is appropriate and very convenient
490
- for local connections on a single-user workstation. It is usually
491
- <emphasis>not</> appropriate by itself on a multiuser machine.
492
- However, you may be able to use <literal>trust</> even on a multiuser
493
- machine, if you restrict access to the postmaster's socket file using
494
- file-system permissions. To do this, set the parameter
487
+ <literal>trust</> authentication is appropriate and very
488
+ convenient for local connections on a single-user workstation. It
489
+ is usually <emphasis>not</> appropriate by itself on a multiuser
490
+ machine. However, you may be able to use <literal>trust</> even
491
+ on a multiuser machine, if you restrict access to the postmaster's
492
+ socket file using file -system permissions. To do this, set the
495
493
<varname>unix_socket_permissions</varname> (and possibly
496
- <varname>unix_socket_group</varname>) in <filename>postgresql.conf</>,
497
- as described in <xref linkend="runtime-config-general">. Or you could
498
- set <varname>unix_socket_directory</varname> to place the socket file
499
- in a suitably restricted directory.
494
+ <varname>unix_socket_group</varname>) configuration parameters as
495
+ described in <xref linkend="runtime-config-general">. Or you
496
+ could set the <varname>unix_socket_directory</varname>
497
+ configuration parameter to place the socket file in a suitably
498
+ restricted directory.
500
499
</para>
501
500
502
501
<para>
0 commit comments