FM / dbconfig-common

/usr/share/doc/dbconfig-common

Name	Size	Mode	Actions
dbapp-policy.html/	-	0755	rm
dbconfig-common.html/	-	0755	rm
examples/	-	0755	rm
changelog.gz	1543	0644	edit dl rm
copyright	10023	0644	edit dl rm
dbapp-policy.pdf.gz	80915	0644	edit dl rm
dbapp-policy.ps.gz	93012	0644	edit dl rm
dbapp-policy.txt.gz	2859	0644	edit dl rm
dbconfig-common-design.html	4599	0644	edit dl rm
dbconfig-common.pdf.gz	123144	0644	edit dl rm
dbconfig-common.ps.gz	132108	0644	edit dl rm
dbconfig-common.txt.gz	8128	0644	edit dl rm
README.Debian	37	0644	edit dl rm
README.pgsql	1434	0644	edit dl rm
THANKS	826	0644	edit dl rm
TODO.gz	2435	0644	edit dl rm
TRANSLATORS	1286	0644	edit dl rm

Edit: /usr/share/doc/dbconfig-common/README.pgsql (1434B)

Helpful information for users who are using postgresql databases.

AUTHENTICATION METHODS

Postgres supports many types of authentication methods. dbconfig-common
currently classifies them into two families: "ident", and "password".  The
former consists of local "peer" and remote postgresql "ident" type connections.
and the latter consists of all the postgresql connections that require a
password (password, crypt, md5, maybe pam/krb5).

For "ident" (=peer) connections on a local host, the server will check that the
owner of the local unix socket is authorized to connect to the database.

For "ident" connections on a remote host, the server will use an rfc 1413 based
ident connection to establish identification. This is probably a bad idea, as
ident is easily spoofable in non-secured networks.

For "password" connections, the psql client will send along passwords with its
connection attempts to the server. The server will then pass the password to
whatever authentication backends it's configured to use. Note that
dbconfig-common has no control over whether or not the password is sent
cleartext over the network (see USING SSL), so you should be aware of the
security risks involved with network based connections.

USING SSL

You must also configure your server to use SSL, which is beyond the scope of
this document. See:

http://developer.postgresql.org/docs/postgres/ssl-tcp.html

for directions on how to do that.

Helpful information for users who are using postgresql databases. AUTHENTICATION METHODS Postgres supports many types of authentication methods. dbconfig-common currently classifies them into two families: "ident", and "password". The former consists of local "peer" and remote postgresql "ident" type connections. and the latter consists of all the postgresql connections that require a password (password, crypt, md5, maybe pam/krb5). For "ident" (=peer) connections on a local host, the server will check that the owner of the local unix socket is authorized to connect to the database. For "ident" connections on a remote host, the server will use an rfc 1413 based ident connection to establish identification. This is probably a bad idea, as ident is easily spoofable in non-secured networks. For "password" connections, the psql client will send along passwords with its connection attempts to the server. The server will then pass the password to whatever authentication backends it's configured to use. Note that dbconfig-common has no control over whether or not the password is sent cleartext over the network (see USING SSL), so you should be aware of the security risks involved with network based connections. USING SSL You must also configure your server to use SSL, which is beyond the scope of this document. See: http://developer.postgresql.org/docs/postgres/ssl-tcp.html for directions on how to do that.