From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rob Sargent <robjsargent@gmail.com>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Pg Docs <pgsql-docs@lists.postgresql.org>
Subject: Re: ssl file permission
Date: Sat, 26 Sep 2020 14:38:50 -0400
Message-ID: <5922.1601145530@sss.pgh.pa.us> (raw)
In-Reply-To: <AA9B61E4-0611-45A7-A5D0-460E2E0C9887@gmail.com>
References: <CABUevEw71x6hJa-GMP6api1C9pZre4XgLn2cUX9oZcZvniRWPw@mail.gmail.com>
<AA9B61E4-0611-45A7-A5D0-460E2E0C9887@gmail.com>
Rob Sargent <robjsargent@gmail.com> writes:
> Sorry. Execute permission for owner may have been on prior to chmod og-rwx . I thought that might be a problem and 600 eliminates that
It seems highly unlikely that openssl would write the file with x
permission turned on. Even if it did, there's no particular
reason for us to insist on changing it.
>> That said, it might be a good idea to be consistent since we seem to use a mix of different styles of chmod.
There is that. But I think the "og-rwx" style is more recommendable,
if we're going to try to standardize.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: tgl@sss.pgh.pa.us, robjsargent@gmail.com, magnus@hagander.net, pgsql-docs@lists.postgresql.org
Subject: Re: ssl file permission
In-Reply-To: <5922.1601145530@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox