+--+--
f| t| t| f
(1 row)
Is this a bug? Should I not be comparing intervals? It would seem the
interval type has enough information to give the correct answer here.
Regards,
Frazer McLean
sl_ca_file`. Apparently, it must be a CRL
generated from the root concatenated to a CRL generated from the
intermediate, and then it works.
[1]:
https://github.com/RazerM/postgres_crl_test/blob/dd9ef3ac4dd74d1cdfc6403899a09d954fd9622a/intermediate-config.txt#L99
Kind regards,
Frazer McLean
--
Sent
I found a solution to the problem, which I’l send here to help those
who find the original email via search.
The intermediate CRL file must be concatenated to CRL files going back
to the root CA.
On 26 Feb 2017, at 15:42, Frazer McLean wrote:
Hi,
I was trying to set up PostgreSQL to use a
://postgrespro.com/list/thread-id/1163456
Kind regards,
Frazer McLean
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
On Tue, 23 Feb 2016, at 17:20, Adrian Klaver wrote:
> Where did you install Postgres from and what version of OpenSSL was it
> compiled against?
I now realise that I wasn't compiling PostgreSQL against my
self-compiled openssl. After adding --with-includes and --with-libraries
to configure I have
Hi,
I am using PostgreSQL 9.4.6 and openssl 1.0.2f. If my server or client
certificate use SHA256, I get the following error on the client:
psql: SSL error: tlsv1 alert decrypt error
And the following log message on the server:
LOG: could not accept SSL connection: unknown message digest algor