Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Adjust user-facing documentation to explain why we don't check

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)postgresql(dot)org>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Date: 2007-02-20 19:46:40
Message-ID: 45DB5020.8080800@dunslane.net (view raw or flat)
Thread:
Lists: pgsql-committers
Dave Page wrote:
> I think the only thing you could do would be to specify that the user
> and only the user have full control over the file. *Any* other ACL
> entries, deny or allow, are not allowed. Access via a group is not allowed.
>   


Are these conditions true of the default location? If not, then either 
this list is too restrictive or the comment we just committed is wrong 
even for that location.

I think the permissions on the default are probably good enough, so we 
should look for a similar ACL.

cheers

andrew


In response to

Responses

pgsql-committers by date

Next:From: Magnus HaganderDate: 2007-02-20 19:47:10
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Previous:From: Dave PageDate: 2007-02-20 19:42:50
Subject: Re: pgsql: Adjust user-facing documentation to explain why we don't check

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group