|PostgreSQL Reference Manual - Volume 3 - Server Administration Guide|
by The PostgreSQL Global Development Group
Paperback (6"x9"), 204 pages
RRP £13.95 ($24.95)
Sales of this book support the PostgreSQL project! Get a printed copy>>>
7.2.1 Trust authentication
trust authentication is specified,
PostgreSQL assumes that anyone who can
connect to the server is authorized to access the database with
whatever database user name they specify (including superusers).
Of course, restrictions made in the
user columns still apply.
This method should only be used when there is adequate
operating-system-level protection on connections to the server.
trust authentication is appropriate and very
convenient for local connections on a single-user workstation. It
is usually not appropriate by itself on a multiuser
machine. However, you may be able to use
on a multiuser machine, if you restrict access to the server's
Unix-domain socket file using file-system permissions. To do this, set the
unix_socket_permissions (and possibly
unix_socket_group) configuration parameters as
described in section 4.3 Connections and Authentication. Or you
could set the
configuration parameter to place the socket file in a suitably
Setting file-system permissions only helps for Unix-socket connections.
Local TCP/IP connections are not restricted by it; therefore, if you want
to use file-system permissions for local security, remove the
127.0.0.1 ... line from ‘pg_hba.conf’, or change it to a
trust authentication method.
trust authentication is only suitable for TCP/IP connections
if you trust every user on every machine that is allowed to connect
to the server by the ‘pg_hba.conf’ lines that specify
trust. It is seldom reasonable to use
for any TCP/IP connections other than those from
|ISBN 0954612043||PostgreSQL Reference Manual - Volume 3 - Server Administration Guide||See the print edition|