|
39 | 39 | #
|
40 | 40 | # host DBNAME IP_ADDRESS ADDRESS_MASK USERAUTH [AUTH_ARGUMENT]
|
41 | 41 | #
|
42 |
| -# DBNAME is the name of a Postgres database, or "all" to indicate all |
| 42 | +# DBNAME is the name of a PostgreSQL database, or "all" to indicate all |
43 | 43 | # databases.
|
44 | 44 | #
|
45 | 45 | # IP_ADDRESS and ADDRESS_MASK are a standard dotted decimal IP address and
|
|
48 | 48 | #
|
49 | 49 | # USERAUTH is a keyword indicating the method used to authenticate the
|
50 | 50 | # user, i.e. to determine that the principal is authorized to connect
|
51 |
| -# under the Postgres username he supplies in his connection parameters. |
| 51 | +# under the PostgreSQL username he supplies in his connection parameters. |
52 | 52 | #
|
53 | 53 | # ident: Authentication is done by the ident server on the remote
|
54 | 54 | # host, via the ident (RFC 1413) protocol. AUTH_ARGUMENT, if
|
55 | 55 | # specified, is a map name to be found in the pg_ident.conf file.
|
56 |
| -# That table maps from ident usernames to Postgres usernames. The |
| 56 | +# That table maps from ident usernames to PostgreSQL usernames. The |
57 | 57 | # special map name "sameuser" indicates an implied map (not found
|
58 | 58 | # in pg_ident.conf) that maps every ident username to the identical
|
59 |
| -# Postgres username. |
| 59 | +# PostgreSQL username. |
60 | 60 | #
|
61 | 61 | # trust: No authentication is done. Trust that the user has the
|
62 |
| -# authority to user whatever username he says he does. |
63 |
| -# Before Postgres Version 6, all authentication was this way. |
| 62 | +# authority to use whatever username he specifies. Before |
| 63 | +# PostgreSQL version 6, all authentication was done this way. |
64 | 64 | #
|
65 | 65 | # reject: Reject the connection.
|
66 | 66 | #
|
67 | 67 | # password: Authentication is done by matching a password supplied in clear
|
68 |
| -# by the host. If AUTH_ARGUMENT is specified then the password is |
69 |
| -# compared with the user's entry in that file (in the $PGDATA |
| 68 | +# by the host. If AUTH_ARGUMENT is specified then the password |
| 69 | +# is compared with the user's entry in that file (in the $PGDATA |
70 | 70 | # directory). See pg_passwd(1). If it is omitted then the
|
71 | 71 | # password is compared with the user's entry in the pg_shadow
|
72 | 72 | # table.
|
|
90 | 90 | #
|
91 | 91 | # The format is the same as that of the "host" record type except that the
|
92 | 92 | # IP_ADDRESS and ADDRESS_MASK are omitted and the "ident", "krb4" and "krb5"
|
93 |
| -# values of USERAUTH are no allowed. |
| 93 | +# values of USERAUTH are not allowed. |
94 | 94 |
|
95 |
| -# For backwards compatibility, PostgreSQL also accepts pre-Version 6 records, |
| 95 | +# For backwards compatibility, PostgreSQL also accepts pre-version 6 records, |
96 | 96 | # which look like:
|
97 | 97 | #
|
98 | 98 | # all 127.0.0.1 0.0.0.0
|
|
119 | 119 | #host all 192.168.0.0 255.255.255.0 ident omicron
|
120 | 120 | #
|
121 | 121 | # The above would allow users from 192.168.0.x hosts to connect to any
|
122 |
| -# database, but if e.g. Ident says the user is "bryanh" and he requests to |
123 |
| -# connect as Postgres user "guest1", the connection is only allowed if |
| 122 | +# database, but if Ident says the user is "bryanh" and he requests to |
| 123 | +# connect as PostgreSQL user "guest1", the connection is only allowed if |
124 | 124 | # there is an entry for map "omicron" in pg_ident.conf that says "bryanh" is
|
125 | 125 | # allowed to connect as "guest1".
|
126 | 126 |
|
|
0 commit comments