postgresql/templates/pg_hba.conf

# PostgreSQL Client Authentication Configuration File
# ===================================================
#
# Refer to the "Client Authentication" section in the PostgreSQL
# documentation for a complete description of this file.  A short
# synopsis follows.
#
# This file controls: which hosts are allowed to connect, how clients
# are authenticated, which PostgreSQL user names they can use, which
# databases they can access.  Records take one of these forms:
#
# local      DATABASE  USER  METHOD  [OPTIONS]
# host       DATABASE  USER  CIDR-ADDRESS  METHOD  [OPTIONS]
# hostssl    DATABASE  USER  CIDR-ADDRESS  METHOD  [OPTIONS]
# hostnossl  DATABASE  USER  CIDR-ADDRESS  METHOD  [OPTIONS]
#
# (The uppercase items must be replaced by actual values.)
#
# The first field is the connection type: "local" is a Unix-domain
# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
# plain TCP/IP socket.
#
# DATABASE can be "all", "sameuser", "samerole", "replication", a
# database name, or a comma-separated list thereof.
#
# USER can be "all", a user name, a group name prefixed with "+", or a
# comma-separated list thereof.  In both the DATABASE and USER fields
# you can also write a file name prefixed with "@" to include names
# from a separate file.
#
# CIDR-ADDRESS specifies the set of hosts the record matches.  It is
# made up of an IP address and a CIDR mask that is an integer (between
# 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies the number
# of significant bits in the mask.  Alternatively, you can write an IP
# address and netmask in separate columns to specify the set of hosts.
# Instead of a CIDR-address, you can write "samehost" to match any of
# the server's own IP addresses, or "samenet" to match any address in
# any subnet that the server is directly connected to.
#
# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
# "krb5", "ident", "pam", "ldap", "radius" or "cert".  Note that
# "password" sends passwords in clear text; "md5" is preferred since
# it sends encrypted passwords.
#
# OPTIONS are a set of options for the authentication in the format
# NAME=VALUE.  The available options depend on the different
# authentication methods -- refer to the "Client Authentication"
# section in the documentation for a list of which options are
# available for which authentication methods.
#
# Database and user names containing spaces, commas, quotes and other
# special characters must be quoted.  Quoting one of the keywords
# "all", "sameuser", "samerole" or "replication" makes the name lose
# its special character, and just match a database or username with
# that name.
#
# This file is read on server startup and when the postmaster receives
# a SIGHUP signal.  If you edit the file on a running system, you have
# to SIGHUP the postmaster for the changes to take effect.  You can
# use "pg_ctl reload" to do that.

# Put your actual configuration here
# ----------------------------------
#
# If you want to allow non-local connections, you need to add more
# "host" records.  In that case you will also need to make PostgreSQL
# listen on a non-local interface via the listen_addresses
# configuration parameter, or via the -i or -h command line switches.

# CAUTION: Configuring the system for local "trust" authentication
# allows any local user to connect as any PostgreSQL user, including
# the database superuser.  If you do not trust all your local users,
# use another authentication method.


# TYPE  DATABASE        USER            CIDR-ADDRESS            METHOD

# "local" is for Unix domain socket connections only
local   all             all                                     trust
# IPv4 local connections:
host    all             all             127.0.0.1/32            trust
# IPv6 local connections:
host    all             all             ::1/128                 trust
1	# PostgreSQL Client Authentication Configuration File
2	# ===================================================
3	#
4	# Refer to the "Client Authentication" section in the PostgreSQL
5	# documentation for a complete description of this file. A short
6	# synopsis follows.
7	#
8	# This file controls: which hosts are allowed to connect, how clients
9	# are authenticated, which PostgreSQL user names they can use, which
10	# databases they can access. Records take one of these forms:
11	#
12	# local DATABASE USER METHOD [OPTIONS]
13	# host DATABASE USER CIDR-ADDRESS METHOD [OPTIONS]
14	# hostssl DATABASE USER CIDR-ADDRESS METHOD [OPTIONS]
15	# hostnossl DATABASE USER CIDR-ADDRESS METHOD [OPTIONS]
16	#
17	# (The uppercase items must be replaced by actual values.)
18	#
19	# The first field is the connection type: "local" is a Unix-domain
20	# socket, "host" is either a plain or SSL-encrypted TCP/IP socket,
21	# "hostssl" is an SSL-encrypted TCP/IP socket, and "hostnossl" is a
22	# plain TCP/IP socket.
23	#
24	# DATABASE can be "all", "sameuser", "samerole", "replication", a
25	# database name, or a comma-separated list thereof.
26	#
27	# USER can be "all", a user name, a group name prefixed with "+", or a
28	# comma-separated list thereof. In both the DATABASE and USER fields
29	# you can also write a file name prefixed with "@" to include names
30	# from a separate file.
31	#
32	# CIDR-ADDRESS specifies the set of hosts the record matches. It is
33	# made up of an IP address and a CIDR mask that is an integer (between
34	# 0 and 32 (IPv4) or 128 (IPv6) inclusive) that specifies the number
35	# of significant bits in the mask. Alternatively, you can write an IP
36	# address and netmask in separate columns to specify the set of hosts.
37	# Instead of a CIDR-address, you can write "samehost" to match any of
38	# the server's own IP addresses, or "samenet" to match any address in
39	# any subnet that the server is directly connected to.
40	#
41	# METHOD can be "trust", "reject", "md5", "password", "gss", "sspi",
42	# "krb5", "ident", "pam", "ldap", "radius" or "cert". Note that
43	# "password" sends passwords in clear text; "md5" is preferred since
44	# it sends encrypted passwords.
45	#
46	# OPTIONS are a set of options for the authentication in the format
47	# NAME=VALUE. The available options depend on the different
48	# authentication methods -- refer to the "Client Authentication"
49	# section in the documentation for a list of which options are
50	# available for which authentication methods.
51	#
52	# Database and user names containing spaces, commas, quotes and other
53	# special characters must be quoted. Quoting one of the keywords
54	# "all", "sameuser", "samerole" or "replication" makes the name lose
55	# its special character, and just match a database or username with
56	# that name.
57	#
58	# This file is read on server startup and when the postmaster receives
59	# a SIGHUP signal. If you edit the file on a running system, you have
60	# to SIGHUP the postmaster for the changes to take effect. You can
61	# use "pg_ctl reload" to do that.
62
63	# Put your actual configuration here
64	# ----------------------------------
65	#
66	# If you want to allow non-local connections, you need to add more
67	# "host" records. In that case you will also need to make PostgreSQL
68	# listen on a non-local interface via the listen_addresses
69	# configuration parameter, or via the -i or -h command line switches.
70
71	# CAUTION: Configuring the system for local "trust" authentication
72	# allows any local user to connect as any PostgreSQL user, including
73	# the database superuser. If you do not trust all your local users,
74	# use another authentication method.
75
76
77	# TYPE DATABASE USER CIDR-ADDRESS METHOD
78
79	# "local" is for Unix domain socket connections only
80	local all all trust
81	# IPv4 local connections:
82	host all all 127.0.0.1/32 trust
83	# IPv6 local connections:
84	host all all ::1/128 trust