pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Michael Paquier <michael.paquier@gmail.com>
Cc: Andreas Karlsson <andreas@proxel.se>
Cc: Michael Banck <michael.banck@credativ.de>
Cc: Peter Geoghegan <pg@heroku.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: [PATCH] Reload SSL certificates on SIGHUP
Date: Tue, 3 Jan 2017 09:34:38 -0500
Message-ID: <f902fcb1-e0fd-2051-b89f-ed273ad5eb94@2ndquadrant.com> (raw)
In-Reply-To: <29982.1483412575@sss.pgh.pa.us>
References: <28784.1440554271@sss.pgh.pa.us>
	<861d27e2-a642-2725-ae31-e375962ab700@proxel.se>
	<fb936d6f-6b83-702f-0b46-6aeef64bf7d3@proxel.se>
	<CAB7nPqSFMTfOdWev=+pTHQAb7bSoYBnm-=+CD5ay59v4c4JvUw@mail.gmail.com>
	<cf48a889-e890-0441-a1ed-57aea18c4b23@proxel.se>
	<0927799d-9f32-7b40-4fe3-04a281365b7a@proxel.se>
	<CAB7nPqT0pufs3b9W5XMMDEJ4XXDbN2x73Cpm-XaZCzwGTXRFeA@mail.gmail.com>
	<CAB7nPqQq_TUe4v0U_jPAYo5xkEo9Qnj94U5sddeRBtjSPMXXQQ@mail.gmail.com>
	<2c1d1551-fd71-113f-7f45-f2379884bf85@proxel.se>
	<CAB7nPqR=8Q9FSbj8PL2oOL2FRmAiqOh8Tqj6tuyqDard4zeuXA@mail.gmail.com>
	<CAB7nPqTHXFJATf+aeqDLRAA_6Y5p2v6AoV_AtNy=ZdCjxOjyEQ@mail.gmail.com>
	<6d45be21-637b-c802-75e7-1ea634ed4089@proxel.se>
	<CAB7nPqThxqDOt_pmJ0d4hHogtmZg=uh=Toez+WyOZzwaCZNSCg@mail.gmail.com>
	<05677cd3-63b2-b15b-7afd-798e34e607c7@proxel.se>
	<CAB7nPqQU50-UMuFcffmynDbH7_kBx3N-Q3ujL-nM2OF3X8biMA@mail.gmail.com>
	<16e282a4-2573-f629-09e8-e6b0ac615890@2ndquadrant.com>
	<29982.1483412575@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 1/2/17 10:02 PM, Tom Lane wrote:
> Before we leave this area, though, there is a loose end that requires
> more thought.  That is, what about passphrase-protected server keys?

I don't have experience with this in practice, but my hunch would be
that you can continue to use passphrases as before, but the new reload
functionality is effectively not supported.  That is, if you use
passphrases and make a key change, you need to do a full restart.

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



view thread (69+ messages)  latest in thread

Message-ID: <f902fcb1-e0fd-2051-b89f-ed273ad5eb94@2ndquadrant.com>
Permalink:  ../f902fcb1-e0fd-2051-b89f-ed273ad5eb94@2ndquadrant.com/
Also on:    postgresql.org/message-id/f902fcb1-e0fd-2051-b89f-ed273ad5eb94@2ndquadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, tgl@sss.pgh.pa.us, michael.paquier@gmail.com, andreas@proxel.se, michael.banck@credativ.de, pg@heroku.com
  Subject: Re: [PATCH] Reload SSL certificates on SIGHUP
  In-Reply-To: <f902fcb1-e0fd-2051-b89f-ed273ad5eb94@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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