Rob Sargent 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 fo
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
> On Sep 26, 2020, at 9:29 AM, Magnus Hagander wrote:
>
>
>
>
>> On Sat, Sep 26, 2020 at 1:23 PM PG Doc comments form
>> wrote:
>> The following document
On Sat, Sep 26, 2020 at 1:23 PM PG Doc comments form
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/12/libpq-ssl.html
> Description:
>
> The instruction to use "chmod og-rwx" could leave the file with read
> permission set.
The following documentation comment has been logged on the website:
Page: https://www.postgresql.org/docs/12/libpq-ssl.html
Description:
The instruction to use "chmod og-rwx" could leave the file with read
permission set. Elsewhere the suggestion is "chmod 600".
