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 45DB54CA.7030906@postgresql.org
обсуждение исходный текст
Ответ на Re: pgsql: Adjust user-facing documentation to explain why we don't check  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: pgsql: Adjust user-facing documentation to explain why we don't check  (Andrew Dunstan <andrew@dunslane.net>)
Список pgsql-committers
Magnus Hagander wrote:
> Dave Page wrote:
>> Magnus Hagander wrote:
>>> It would break insofar that it wouldn't work. the pgpass file. It will
>>> of course not break *windows*, but people will consider PostgreSQL broken.
>>>
>> Please explain why it won't work. *Existing* pgpass files would need to
>> be secured, but that could be handled with documentation and suitable
>> checks and hints in pgAdmin/libpq. New pgpass files created by pgAdmin
>> (or other apps) would simply need to be secured by those apps at
>> creation time.
>
> Files created using notepad (or whatever) will not work. Unless you
> manually fiddle around with the permissions.

If you are savvy enough to read the docs, un-hide the directory, and
manually create the file in the correct format, surely you can also run
cacls on it? We expect *nix users to run chmod on theirs after all.

I don't see this as such a big issue.

Regards, Dave.

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

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: pgsql: Adjust user-facing documentation to explain why we don't check
Следующее
От: Andrew Dunstan
Дата:
Сообщение: Re: pgsql: Adjust user-facing documentation to explain why we don't check