pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
ssl file permission
4+ messages / 4 participants
[nested] [flat]

* ssl file permission
@ 2020-09-25 22:04  PG Doc comments form <noreply@postgresql.org>
  0 siblings, 1 reply; 4+ messages in thread

From: PG Doc comments form @ 2020-09-25 22:04 UTC (permalink / raw)
  To: pgsql-docs@lists.postgresql.org; +Cc: robjsargent@gmail.com

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".


^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: ssl file permission
@ 2020-09-26 15:28  Magnus Hagander <magnus@hagander.net>
  parent: PG Doc comments form <noreply@postgresql.org>
  0 siblings, 1 reply; 4+ messages in thread

From: Magnus Hagander @ 2020-09-26 15:28 UTC (permalink / raw)
  To: Rob Sargent <robjsargent@gmail.com>; Pg Docs <pgsql-docs@lists.postgresql.org>

On Sat, Sep 26, 2020 at 1:23 PM PG Doc comments form <noreply@postgresql.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/ <http://www.hagander.net/;
 Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/;

^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: ssl file permission
@ 2020-09-26 15:54  Rob Sargent <robjsargent@gmail.com>
  parent: Magnus Hagander <magnus@hagander.net>
  0 siblings, 1 reply; 4+ messages in thread

From: Rob Sargent @ 2020-09-26 15:54 UTC (permalink / raw)
  To: Magnus Hagander <magnus@hagander.net>; +Cc: Pg Docs <pgsql-docs@lists.postgresql.org>

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@hagander.net> wrote:
> 
> 
> 
> 
>> On Sat, Sep 26, 2020 at 1:23 PM PG Doc comments form <noreply@postgresql.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/

^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: ssl file permission
@ 2020-09-26 18:38  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Rob Sargent <robjsargent@gmail.com>
  0 siblings, 0 replies; 4+ messages in thread

From: Tom Lane @ 2020-09-26 18:38 UTC (permalink / raw)
  To: Rob Sargent <robjsargent@gmail.com>; +Cc: Magnus Hagander <magnus@hagander.net>; Pg Docs <pgsql-docs@lists.postgresql.org>

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





^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2020-09-26 18:38 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2020-09-25 22:04 ssl file permission PG Doc comments form <noreply@postgresql.org>
2020-09-26 15:28 ` Magnus Hagander <magnus@hagander.net>
2020-09-26 15:54   ` Rob Sargent <robjsargent@gmail.com>
2020-09-26 18:38     ` Tom Lane <tgl@sss.pgh.pa.us>

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