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 1l5xfS-0000m2-KW for pgsql-hackers@arkaria.postgresql.org; Sat, 30 Jan 2021 21:20:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1l5xfR-0002tk-HJ for pgsql-hackers@arkaria.postgresql.org; Sat, 30 Jan 2021 21:20:29 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l5xfQ-0002td-RG for pgsql-hackers@lists.postgresql.org; Sat, 30 Jan 2021 21:20:29 +0000 Received: from forward2-smtp.messagingengine.com ([66.111.4.226]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1l5xfL-00035c-Ts for pgsql-hackers@postgresql.org; Sat, 30 Jan 2021 21:20:28 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailforward.nyi.internal (Postfix) with ESMTP id CD6A619537FC; Sat, 30 Jan 2021 16:20:21 -0500 (EST) Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sat, 30 Jan 2021 16:20:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=2sBlSYb0daTgCb8fd9BNiv9SJCagpIh4qbsItF7K/ tc=; b=RZNHVE6qSBXMdp4y7YP3rpThyDmMMO+iS1cSZYklJwOTE3DTDRjwmJYC3 aXcZBMEwG7DdpVu2f6Ek1bBDb3Yy0I5CjZtImr3JI2Jhx7MPKiJ3pWnppBK+wsj1 dpAevN8cxDLgBWVqAA0hHgpCohuSaihqoRabiY60bkzX35aQwwBg9Kuy1pfWZlMx sP33q20mv1w4TzPdAmLDC5bx/bRhfZapnfEoKlPrGACVjWieNUL5ytt1U4QpwRQ7 vjaEd56qZzVcYDDx9gbbklvJyOcWs450GLCl+xEXb6QBbcyNxKRDQzGSJ7AwlIQL NLVq0d+139vzBHEQlySE2Gk3DbYyQ== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrfeeggdduhedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefuvfhfhfhokffffgggjggtgfesth ejredttdefheenucfhrhhomheprfgvthgvrhcugfhishgvnhhtrhgruhhtuceophgvthgv rhdrvghishgvnhhtrhgruhhtsegvnhhtvghrphhrihhsvggusgdrtghomheqnecuggftrf grthhtvghrnhepgfethfeguefgtddvudeljeejjeefgfeuudetveevkeellefhheehfeeg tddtueeunecuffhomhgrihhnpegtrhhlrdgshienucfkphepkeejrddujeejrdeiledrud egtdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehp vghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Received: from april.pezone.net (p57b1458c.dip0.t-ipconnect.de [87.177.69.140]) by mail.messagingengine.com (Postfix) with ESMTPA id 78C1E1080063; Sat, 30 Jan 2021 16:20:20 -0500 (EST) Subject: Re: Is it worth accepting multiple CRLs? To: Kyotaro Horiguchi References: <20200831.180302.1762036380359974457.horikyota.ntt@gmail.com> <591fd449-f475-c2f1-0606-b2a47887c23f@enterprisedb.com> <20210119.091734.2050908166228453830.horikyota.ntt@gmail.com> <20210119.173200.1687041891704633506.horikyota.ntt@gmail.com> Cc: sfrost@snowman.net, pgsql-hackers@postgresql.org From: Peter Eisentraut Organization: EnterpriseDB Message-ID: <516cf19c-840b-3db6-3320-4145d49c24d8@enterprisedb.com> Date: Sat, 30 Jan 2021 22:20:19 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20210119.173200.1687041891704633506.horikyota.ntt@gmail.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 2021-01-19 09:32, Kyotaro Horiguchi wrote: > At Tue, 19 Jan 2021 09:17:34 +0900 (JST), Kyotaro Horiguchi wrote in >> By the way we can do the same thing on CA file/dir, but I personally >> think that the benefit from the specify-by-directory for CA files is >> far less than CRL files. So I'm not going to do this for CA files for >> now. > > This is it. A new guc ssl_crl_dir and connection option crldir are > added. This looks pretty good to me overall. You need to update the expected result of the postgres_fdw test. Also check your patch for whitespace errors with git diff --check or similar. > One problem raised upthread is the footprint for test is quite large > because all certificate and key files are replaced by this patch. I > think we can shrink the footprint by generating that files on-demand > but that needs openssl frontend to be installed on the development > environment. I don't understand why you need to recreate all these files. All your patch should contain are the new *.r0 files that are computed from the existing *.crl files. Nothing else should change, AIUI. Some of the makefile rules for generating the CRL files need some refinement. In +ssl/root+server-crldir: ssl/server.crl + mkdir ssl/root+server-crldir + cp ssl/server.crl ssl/root+server-crldir/`openssl crl -hash -noout -in ssl/server.crl`.r0 + cp ssl/root.crl ssl/root+server-crldir/`openssl crl -hash -noout -in ssl/root.crl`.r0 +ssl/root+client-crldir: ssl/client.crl + mkdir ssl/root+client-crldir + cp ssl/client.crl ssl/root+client-crldir/`openssl crl -hash -noout -in ssl/client.crl`.r0 + cp ssl/root.crl ssl/root+client-crldir/`openssl crl -hash -noout -in ssl/root.crl`.r0 the rules should also have a dependency on ssl/root.crl in addition to ssl/server.crl. By the way: - print $sslconf "ssl_crl_file='root+client.crl'\n"; + print $sslconf "ssl_crl_file='$crlfile'\n" if (defined $crlfile); + print $sslconf "ssl_crl_dir='$crldir'\n" if (defined $crldir); Trailing "if" doesn't need parentheses.