Re: [BUGS] BUG #14586: Permissions of recovery.conf are different inplain and tar-format

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [BUGS] BUG #14586: Permissions of recovery.conf are different inplain and tar-format
Дата
Msg-id CAB7nPqQ9st=Hs6vpcxqp0_JVcDK7rn6zSCPb83znSg0yU+s2+A@mail.gmail.com
обсуждение исходный текст
Ответ на [BUGS] BUG #14586: Permissions of recovery.conf are different in plain andtar-format  (markus@braeunig.biz)
Ответы Re: [BUGS] BUG #14586: Permissions of recovery.conf are different inplain and tar-format
Список pgsql-bugs
On Fri, Mar 10, 2017 at 5:00 PM,  <markus@braeunig.biz> wrote:
> The option "--write-recovery-conf" of pg_basebackup creates a valid
> recovery.conf but misses to apply secure file permissions when the default
> format (plain) is used.
>
> If you tar the result (-F t), the recovery.conf inside the base.tar has the
> permissions 0600.
> In plain format the umask of the actual user is applied and the permissions
> are e.g. 0644.
>
> Because plain passwords are possible in this file, I would suggest to unify
> this behavior and change the permissions to 0600 in both cases.

It does not matter much. Backup folder created by pg_basebackup has
0700 as umask.
-- 
Michael


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

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

Предыдущее
От: Neo Liu
Дата:
Сообщение: Re: [BUGS] BUG #14588: Postgres process blocked on semop
Следующее
От: Markus Bräunig
Дата:
Сообщение: Re: [BUGS] BUG #14586: Permissions of recovery.conf are different inplain and tar-format