Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kMCXS-00040h-AH for pgsql-docs@arkaria.postgresql.org; Sat, 26 Sep 2020 15:55:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kMCXR-0007xN-8r for pgsql-docs@arkaria.postgresql.org; Sat, 26 Sep 2020 15:55:05 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kMCXR-0007uv-3q for pgsql-docs@lists.postgresql.org; Sat, 26 Sep 2020 15:55:05 +0000 Received: from mail-ot1-x342.google.com ([2607:f8b0:4864:20::342]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kMCXO-0007PH-UN for pgsql-docs@lists.postgresql.org; Sat, 26 Sep 2020 15:55:04 +0000 Received: by mail-ot1-x342.google.com with SMTP id a2so5258941otr.11 for ; Sat, 26 Sep 2020 08:55:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=Jdlc95TmaZF0xHqhD9021lE8GmgMpEP40X5GrJrXX0o=; b=BTvMvZ9fSmKNtFZBmnJZUtylrQlfk/Mp/J/r/GlEUDF4d+ci7D80nf1L28Ope1n2Pf 84EVqKkJ5tsWXL2Xi8pyKkAeKFFL/tuVecP5CzqqFcMisl0HbDwwq+9cPbrkPuWhf5Wc j0UXWU6qHCdp/STmE1izlArVVtbuXVn5vPpjidt3FmQ8Y7VyOh1K+r5TlU34ejUemGwx OdZxAKP9MS4nIrZhohil0tJT1g3DbKVCQMrklOs4CKDLqi3wdEn4nK/ZYj/eOirGyINw kqtAzwzbqCC+e7j1XxbRQzyRn99e86CPEhksyTcp02fRXE1xB8bQgEajepwefA6FLdSj iS0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=Jdlc95TmaZF0xHqhD9021lE8GmgMpEP40X5GrJrXX0o=; b=B+N09RoEc8QaVbWyQ3RZh3tKskz1b5972m8+Z9qRC4GfARWyL8SVIchiV6wMvbIS5b xwUFR+eL5JQz9KyfzUO/G30m50XMPpygYrxUfeZihXVQnu1BEaJQj2e+Nj6AltuxLaMy syW9YuADY5WWE/VOa70jfPtkqwhSTbMHDNOmZD+u1xh2Xg5GNvmYrciqdpWTNqcIqjkh ivWCCPp6bAVadzz5b8JP5qCvkHkiwGlcNT15+oDgyfbfmKdZMq49SI3YdGChkDEGrMEO g9Nl8RZ+rHYpbcoNm5KAbLIZD4XbKrWcMnIHuhqH9J5V5fQq0ks4qhy/bEe3SlxSDmU2 FrKQ== X-Gm-Message-State: AOAM533ox/oy1iVk+G4dS0vaJRtx4e0uO8WsQWFUIkHApA8UbBP0OKHK OP5tKrTymWjn4eEq39VttwA= X-Google-Smtp-Source: ABdhPJy1j93SsYBVQr4RHiZtfEX8qbhjqJVgRupBqBWWjopQYR9ofjqb3E76lo9whjChH7Z7kiTAWg== X-Received: by 2002:a05:6830:22ce:: with SMTP id q14mr3676781otc.72.1601135700961; Sat, 26 Sep 2020 08:55:00 -0700 (PDT) Received: from ?IPv6:2601:681:5500:dde0:216d:d6c4:2de2:ae49? ([2601:681:5500:dde0:216d:d6c4:2de2:ae49]) by smtp.gmail.com with ESMTPSA id p69sm1475641oic.27.2020.09.26.08.55.00 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sat, 26 Sep 2020 08:55:00 -0700 (PDT) Content-Type: multipart/alternative; boundary=Apple-Mail-3CE1A700-7B33-4F7B-AB2B-B71534E021D1 Content-Transfer-Encoding: 7bit From: Rob Sargent Mime-Version: 1.0 (1.0) Subject: Re: ssl file permission Date: Sat, 26 Sep 2020 09:54:59 -0600 Message-Id: References: Cc: Pg Docs In-Reply-To: To: Magnus Hagander X-Mailer: iPhone Mail (17H35) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --Apple-Mail-3CE1A700-7B33-4F7B-AB2B-B71534E021D1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable 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: >=20 > =EF=BB=BF >=20 >=20 >> On Sat, Sep 26, 2020 at 1:23 PM PG Doc comments form wrote: >> The following documentation comment has been logged on the website: >>=20 >> Page: https://www.postgresql.org/docs/12/libpq-ssl.html >> Description: >>=20 >> The instruction to use "chmod og-rwx" could leave the file with read >> permission set. Elsewhere the suggestion is "chmod 600". >=20 >=20 > Not sure what you mean here -- how could it leave it with read permission s= et? >=20 > (Obviously it could for the owner, but 0600 also includes read permissions= for the owner) >=20 > That said, it might be a good idea to be consistent since we seem to use a= mix of different styles of chmod. >=20 > --=20 > Magnus Hagander > Me: https://www.hagander.net/ > Work: https://www.redpill-linpro.com/ --Apple-Mail-3CE1A700-7B33-4F7B-AB2B-B71534E021D1 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Sorry. Execute p= ermission for owner may have been on prior to chmod og-rwx .  I tho= ught that might be a problem and 600 eliminates that
<= br>
On Sep 26, 2020, at 9:29 AM, Magnus Hagander &l= t;magnus@hagander.net> wrote:

=EF=BB=BF


On Sat= , Sep 26, 2020 at 1:23 PM PG Doc comments form <noreply@postgresql.org> wrote:
The following documentation comment has b= een logged on the website:

Page: https://www.postgresql.org/docs/12/libpq-ssl.ht= ml
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 i= t leave it with read permission set?

(Obviously it could f= or the owner, but 0600 also includes read permissions for the owner)

That said, it might be a good idea to be consistent since w= e seem to use a mix of different styles of chmod.

=
--
= --Apple-Mail-3CE1A700-7B33-4F7B-AB2B-B71534E021D1--