@@ -156,19 +156,24 @@ postgres$ <userinput>initdb -D /usr/local/pgsql/data</userinput>
156156 </para>
157157
158158 <para>
159- The default client authentication setup is such that users can connect over
160- the Unix-domain socket to the same database user name as their operating
161- system user names (on operating systems that support this, which are most
162- modern Unix-like systems, but not Windows) and otherwise with a password.
163- To assign a password to the initial database superuser, use one of
159+ However, while the directory contents are secure, the default
160+ client authentication setup allows any local user to connect to the
161+ database and even become the database superuser. If you do not
162+ trust other local users, we recommend you use one of
164163 <command>initdb</command>'s <option>-W</option>, <option>--pwprompt</option>
165- or <option>--pwfile</option> options.<indexterm>
164+ or <option>--pwfile</option> options to assign a password to the
165+ database superuser.<indexterm>
166166 <primary>password</primary>
167167 <secondary>of the superuser</secondary>
168168 </indexterm>
169- This configuration is secure and sufficient to get started. Later, see
170- <xref linkend="client-authentication"/> for more information about setting
171- up client authentication.
169+ Also, specify <option>-A md5</option> or
170+ <option>-A password</option> so that the default <literal>trust</literal> authentication
171+ mode is not used; or modify the generated <filename>pg_hba.conf</filename>
172+ file after running <command>initdb</command>, but
173+ <emphasis>before</emphasis> you start the server for the first time. (Other
174+ reasonable approaches include using <literal>peer</literal> authentication
175+ or file system permissions to restrict connections. See <xref
176+ linkend="client-authentication"/> for more information.)
172177 </para>
173178
174179 <para>