version 1, including all changes.
.
| Rev |
Author |
# |
Line |
| 1 |
perry |
1 |
PG_PASSWD |
| |
|
2 |
!!!PG_PASSWD |
| |
|
3 |
NAME |
| |
|
4 |
SYNOPSIS |
| |
|
5 |
DESCRIPTION |
| |
|
6 |
SEE ALSO |
| |
|
7 |
---- |
| |
|
8 |
!!NAME |
| |
|
9 |
|
| |
|
10 |
|
| |
|
11 |
pg_passwd - change a secondary PostgreSQL password file |
| |
|
12 |
!!SYNOPSIS |
| |
|
13 |
|
| |
|
14 |
|
| |
|
15 |
__pg_passwd__ ''filename'' |
| |
|
16 |
!!DESCRIPTION |
| |
|
17 |
|
| |
|
18 |
|
| |
|
19 |
__pg_passwd__ is a tool for manipulating flat text |
| |
|
20 |
password files. These files can control client |
| |
|
21 |
authentication of the PostgreSQL server. More information |
| |
|
22 |
about setting up this authentication mechanism can be found |
| |
|
23 |
in the ''Administrator's Guide''. |
| |
|
24 |
|
| |
|
25 |
|
| |
|
26 |
The format of a text password file is one entry per line; |
| |
|
27 |
the fields of each entry are separated by colons. The first |
| |
|
28 |
field is the user name, the second field is the encrypted |
| |
|
29 |
password. Other fields are ignored (to allow password files |
| |
|
30 |
to be shared between applications that use similar formats). |
| |
|
31 |
__pg_passwd__ enables users to interactively add entries |
| |
|
32 |
to such a file, to alter passwords of existing entries, and |
| |
|
33 |
to encrypt such passwords. |
| |
|
34 |
|
| |
|
35 |
|
| |
|
36 |
Supply the name of the password file as argument to the |
| |
|
37 |
__pg_passwd__ command. To be used by PostgreSQL, the file |
| |
|
38 |
needs to be located in the server's data directory, and the |
| |
|
39 |
base name of the file needs to be specified in the |
| |
|
40 |
''pg_hba.conf'' access control file. |
| |
|
41 |
|
| |
|
42 |
|
| |
|
43 |
$ __pg_passwd /usr/local/pgsql/data/passwords |
| |
|
44 |
__File __y |
| |
|
45 |
__Username: __guest |
| |
|
46 |
__Password: |
| |
|
47 |
Re-enter password: |
| |
|
48 |
where the Password: and Re-enter password: prompts require the same password input which is not displayed on the terminal. Note that the password is limited to eight useful characters by restrictions of the standard crypt(3) library routine. |
| |
|
49 |
|
| |
|
50 |
|
| |
|
51 |
The original password file is renamed to |
| |
|
52 |
''passwords.bk''. |
| |
|
53 |
|
| |
|
54 |
|
| |
|
55 |
To make use of this password file, put a line like the |
| |
|
56 |
following in ''pg_hba.conf'': |
| |
|
57 |
|
| |
|
58 |
|
| |
|
59 |
host mydb 133.65.96.250 255.255.255.255 password passwords |
| |
|
60 |
which would allow access to database mydb from host 133.65.96.250 using the passwords listed in the ''passwords'' file (and only to the users listed in that file). |
| |
|
61 |
|
| |
|
62 |
|
| |
|
63 |
__Note:__ It is also useful to have entries in a password |
| |
|
64 |
file with empty password fields. (This is different from an |
| |
|
65 |
empty password.) Such entries allow you to restrict users |
| |
|
66 |
who can access the system. These entries cannot be managed |
| |
|
67 |
by __pg_passwd__, but you can edit password files |
| |
|
68 |
manually. |
| |
|
69 |
!!SEE ALSO |
| |
|
70 |
|
| |
|
71 |
|
| |
|
72 |
''PostgreSQL Administrator's Guide'' |
| |
|
73 |
---- |
