From: John Scalia <jayknowsunix@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: SSL certificate revocation file will not load
Date: Wed, 14 Jun 2017 17:55:22 -0400
Message-ID: <68DC7C40-A815-4F80-924A-45C07A463D55@gmail.com> (raw)
In-Reply-To: <23871.1497473425@sss.pgh.pa.us>
References: <CABzCKRCjpiosAEVujuvBN+KOzdaQSJyLuo-TTQdmc98PqcKjNA@mail.gmail.com>
<23871.1497473425@sss.pgh.pa.us>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Well, it turned out that the CRL was in the wrong format. So, I managed to convert it with OpenSSL and it loaded properly. I do have one more question... the Treasury Department, which produces these certificates for us, expires all the CRL's in just 6 hours, so does that mean I'd have to do restart on the database each time I got a new one or would a reload work?
Sent from my iPad
> On Jun 14, 2017, at 4:50 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> John Scalia <jayknowsunix@gmail.com> writes:
>> I've got SSL working without the crl file, but when I set ssl_crl_file to
>> use the one I have, it says FATAL on a restart and no SSL error reported.
>> This is not very helpful.
>
> Did you look into the postmaster log? Experimenting with an intentionally
> corrupted CRL file here, I get log messages along the lines of
>
> 2017-06-14 16:45:15.096 EDT [22759] LOG: parameter "ssl_crl_file" changed to "root+client.crl"
> 2017-06-14 16:45:15.102 EDT [22759] LOG: could not load SSL certificate revocation list file "root+client.crl": bad base64 decode
>
> The actually useful part of that comes out of OpenSSL, and we don't have
> a lot of control about how specific it is ... but there should be
> *something*.
>
> regards, tom lane
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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-admin@postgresql.org
Cc: jayknowsunix@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: SSL certificate revocation file will not load
In-Reply-To: <68DC7C40-A815-4F80-924A-45C07A463D55@gmail.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