From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Pg Docs <pgsql-docs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: ssl file permission |
Date: | 2020-09-26 15:54:59 |
Message-ID: | AA9B61E4-0611-45A7-A5D0-460E2E0C9887@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
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 <magnus(at)hagander(dot)net> wrote:
>
>
>
>
>> On Sat, Sep 26, 2020 at 1:23 PM PG Doc comments form <noreply(at)postgresql(dot)org> 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. Elsewhere the suggestion is "chmod 600".
>
>
> Not sure what you mean here -- how could it leave it with read permission set?
>
> (Obviously it could for the owner, but 0600 also includes read permissions for the owner)
>
> That said, it might be a good idea to be consistent since we seem to use a mix of different styles of chmod.
>
> --
> Magnus Hagander
> Me: https://www.hagander.net/
> Work: https://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2020-09-26 18:38:50 | Re: ssl file permission |
Previous Message | Magnus Hagander | 2020-09-26 15:28:54 | Re: ssl file permission |