From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?Q?Ludovic_Court=C3=A8s?= Subject: Re: Renewing certificates with certbot Date: Wed, 06 Mar 2019 14:42:13 +0100 Message-ID: <87fts0i0ga.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:37947) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h1WoU-0003D3-V0 for guix-devel@gnu.org; Wed, 06 Mar 2019 08:42:27 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h1WoR-0004Y4-6Z for guix-devel@gnu.org; Wed, 06 Mar 2019 08:42:25 -0500 Received: from hera.aquilenet.fr ([2a0c:e300::1]:41296) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1h1WoP-0004Vr-Kf for guix-devel@gnu.org; Wed, 06 Mar 2019 08:42:22 -0500 In-Reply-To: (Julien Lepiller's message of "Fri, 22 Feb 2019 14:49:52 +0100") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Julien Lepiller Cc: guix-devel@gnu.org Hi, Julien Lepiller skribis: > I use certificates from let's encrypt for my website and mail servers, > and found that there was an issue with certificates generated by the > certbot service in Guix: the generated private keys are world-readable > (in a directory that cannot be accessed by anyone but root, so it's OK > I guess). OpenSMTPD is not happy with that though, so I have to chmod > the files every time. I came up with a variant of the deploy-hook > that's presented in the manual, and I'd like to update the example > with it. Here it is: > > ;; Find running nginx and reload its configuration (for certificates) > (define %my-deploy-hook > (program-file > "my-deploy-hook" > #~(let* ((pid (call-with-input-file "/var/run/nginx/pid" read)) > (cert-dir (getenv "RENEWED_LINEAGE")) > (privkey (string-append cert-dir "/privkey.pem"))) > ;; certbot private keys are world-readable by default, and > smtpd complains > ;; about that, refusing to start otherwise > (chmod privkey #o600) > (kill pid SIGHUP)))) > > What do you think? It sounds like a serious issue that private keys are world-readable. Is it a bug on our side or in Certbot? I think we should fix it so that they are never world-readable, rather than document how to work around the bug. WDYT? Thanks, Ludo=E2=80=99.