Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cOnn7-00021M-GC for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Jan 2017 15:47:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1cOnn6-0007SI-UY for pgsql-hackers@arkaria.postgresql.org; Wed, 04 Jan 2017 15:47:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cOnlg-0004Kk-Ho for pgsql-hackers@postgresql.org; Wed, 04 Jan 2017 15:46:24 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1cOnld-0007VV-2P for pgsql-hackers@postgresql.org; Wed, 04 Jan 2017 15:46:24 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 71D9520B7B; Wed, 4 Jan 2017 10:46:19 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Wed, 04 Jan 2017 10:46:19 -0500 DKIM-Signature: v=1; a=rsa-sha1; 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-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=94DEDgBtndPbQfyIxNhtDD0PCxo=; b=KuR1yzspkagFf30lz5Ox lKaTV1lwer1Zkg5DiLBMpWnYxQ01i7HJS1MeVBw8Qla+hwTB6slmQ5Je6axwiK3A m0RYWWRZ7qUB94RmyA6iKh6x/yKal+dTiUC80kiLAgItN+NoyAEL6eYPwCvxokGC SJEA5+9JO5ywiMs03nAdo98= X-ME-Sender: X-Sasl-enc: 4/ipbK1R1WNWiy24a3a7EqWYN3Wby9LW0bBoxz2DhQ0q 1483544779 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 0EE902468C; Wed, 4 Jan 2017 10:46:19 -0500 (EST) Subject: Re: [PATCH] Reload SSL certificates on SIGHUP To: Tom Lane , Andreas Karlsson References: <05677cd3-63b2-b15b-7afd-798e34e607c7@proxel.se> <16e282a4-2573-f629-09e8-e6b0ac615890@2ndquadrant.com> <29982.1483412575@sss.pgh.pa.us> <23913.1483458895@sss.pgh.pa.us> <20995.1483541230@sss.pgh.pa.us> <7fca80da-0274-3f36-eb25-d53f940c1977@proxel.se> <20170104151429.GP18360@tamriel.snowman.net> <1254e97b-a65a-5a63-e938-810507a16d71@proxel.se> <22644.1483543579@sss.pgh.pa.us> Cc: Stephen Frost , Magnus Hagander , Michael Paquier , Michael Banck , Peter Geoghegan , PostgreSQL-development From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Wed, 4 Jan 2017 10:46:28 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.6.0 MIME-Version: 1.0 In-Reply-To: <22644.1483543579@sss.pgh.pa.us> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org On 1/4/17 10:26 AM, Tom Lane wrote: > Andreas Karlsson writes: >> Sorry, I was very unclear. I meant refusing the reload the SSL context >> if there is a pass phrase, but that the rest of the config will be >> reloaded just fine. This will lead to some log spam on every SIGHUP for >> people with a pass phrase but should otherwise work as before. > > How will you know whether there's a pass phrase? One could register a password callback that remembers whether it was called. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers