Re: Java client connection problem on FIPS enabled hosts (with password_encryption = scram-sha-256)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: "McDermott, Becky" <bmcderm(at)sandia(dot)gov>, "pgsql-jdbc(at)lists(dot)postgresql(dot)org" <pgsql-jdbc(at)lists(dot)postgresql(dot)org>
Subject: Re: Java client connection problem on FIPS enabled hosts (with password_encryption = scram-sha-256)
Date: 2022-03-22 22:54:29
Message-ID: 2612178.1647989669@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Tue, Mar 22, 2022 at 03:58:49PM +0000, McDermott, Becky wrote:
>> We have a requirement to run all of our applications on FIPS enabled hosts.

> Is FIPS enabled on the host holding the PostgreSQL instance? I am
> afraid that you may run to run into problems in this case, in the
> shape of a crash in the backend.

I worried about that too in the earlier pgsql-general thread. But the
Java exception trace looks like the error is being thrown client-side.
Also Becky says she can connect successfully with psql, which indicates
that the server-side stack is not subject to those problems you mentioned.

regards, tom lane

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message McDermott, Becky 2022-03-22 23:00:04 RE: [EXTERNAL] Re: Java client connection problem on FIPS enabled hosts (with password_encryption = scram-sha-256)
Previous Message Michael Paquier 2022-03-22 22:49:52 Re: Java client connection problem on FIPS enabled hosts (with password_encryption = scram-sha-256)