RE: [GENERAL] Another access control query - Mailing list pgsql-general

From Nicolas Huillard
Subject RE: [GENERAL] Another access control query
Date
Msg-id 01BF16FC.70C19E10@agen.int.ghs
Whole thread Raw
List pgsql-general
I don't remember if I read this somewhere, or if I simply did it.
Maybe this should be pointed in the doc, but I think this is only a workaround : why should there be separate files
containingpasswords, as soon as the pg_shadow table already contains passwords... 
My advice is that you should keep these files in $PG_DATA, because this directory is protected (full access to the Unix
userpostgres only, and nobody else). 

Yours,

Nicolas

-----Message d'origine-----
De:    Mark Jewiss [SMTP:Mark.Jewiss@knowledge.com]
Date:    vendredi 15 octobre 1999 10:31
À:    Nicolas Huillard
Cc:    pgsql-general@postgreSQL.org
Objet:    RE: [GENERAL] Another access control query

Hello,

On Thu, 14 Oct 1999, Nicolas Huillard wrote:

> You can add a filename to the "password" keyword. Thsi filename contains the username/crypted password of the users
youwant to be able to connect from the servip to the dbX. 
> The lines in pg_hba looks like :
> host    bd1    serverip1 netmask    password    password.username1
> host    bd2    serverip2 netmask    password    password.username2

This is pretty cool, thanks for pointing it out. Does the documentation
still need doing for this, or is my set out of date?

Also, can you specify a path to the password file? I've tried this, but
can't get it to work, so am assuming not, and that it has to be in the
same directory as the pg_hba.conf file, but just want to check.

Regards,

Mark.
--
Mark Jewiss
Knowledge Matters Limited
http://www.knowledge.com


************



pgsql-general by date:

Previous
From: Ryszard Kurek
Date:
Subject: Performance comparation
Next
From: "Moray McConnachie"
Date:
Subject: Re: The Next Step ==> was Re: [GENERAL] stored procedure revisited