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

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: pgsql: Adjust user-facing documentation to explain why we don't check
Дата
Msg-id 45DB5205.3010604@postgresql.org
обсуждение исходный текст
Ответ на Re: pgsql: Adjust user-facing documentation to explain why we don't check  (Andrew Dunstan <andrew@dunslane.net>)
Список 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.


В списке pgsql-committers по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Следующее
От: momjian@postgresql.org (Bruce Momjian)
Дата:
Сообщение: pgsql: Update "encode" documentation to mention that 'escape' only