Re: [EXTERNAL] Re: Java client connection problem on FIPS enabled hosts (with password_encryption = scram-sha-256) - Mailing list pgsql-jdbc

From Michael Paquier
Subject Re: [EXTERNAL] Re: Java client connection problem on FIPS enabled hosts (with password_encryption = scram-sha-256)
Date
Msg-id YjpbP/6q2q48NKaZ@paquier.xyz
Whole thread Raw
In response to RE: [EXTERNAL] Re: Java client connection problem on FIPS enabled hosts (with password_encryption = scram-sha-256)  ("McDermott, Becky" <bmcderm@sandia.gov>)
Responses Re: [EXTERNAL] Re: Java client connection problem on FIPS enabled hosts (with password_encryption = scram-sha-256)  (Dave Cramer <davecramer@postgres.rocks>)
List pgsql-jdbc
On Tue, Mar 22, 2022 at 11:00:04PM +0000, McDermott, Becky wrote:
> Should we be looking at upgrading Postgres to version 14?

If FIPS is enabled on the host running Postgres, you'd better do so.
Now, that would also depend on the version of OpenSSL your builds of
Postgres are linking to (aka pure upstream, patched version, etc.).
--
Michael

Attachment

pgsql-jdbc by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Java client connection problem on FIPS enabled hosts (with password_encryption = scram-sha-256)
Next
From: Dave Cramer
Date:
Subject: Re: [EXTERNAL] Re: Java client connection problem on FIPS enabled hosts (with password_encryption = scram-sha-256)