| From: | Dave Page <dpage(at)postgresql(dot)org> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| 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:54:45 |
| Message-ID: | 45DB5205.3010604@postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Andrew Dunstan wrote:
> 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.
No, as Magnus has pointed out there are almost certainly adminstrator
and system entries in the default ACL - and we don't necessarily know
the local installation well enough to be able to tell if an insecure
entry has been added.
> I think the permissions on the default are probably good enough, so we
> should look for a similar ACL.
We could make that assumption in the the default location, and require a
strict ACL elsewhere.
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Page | 2007-02-20 19:59:03 | Re: pgsql: Adjust user-facing documentation to explain why we don't check |
| Previous Message | Magnus Hagander | 2007-02-20 19:47:10 | Re: pgsql: Adjust user-facing documentation to explain why we don't check |