Re: scram-sha-256 authentication broken in FIPS mode

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Alessandro Gherardi <alessandro(dot)gherardi(at)yahoo(dot)com>
Cc: "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: scram-sha-256 authentication broken in FIPS mode
Date: 2018-09-11 14:32:27
Message-ID: 5aeb058d-e32c-e3e0-e4b1-6469aeeadc2b@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/09/2018 05:02, Michael Paquier wrote:
> Hence, intrinsically, we are in contradiction with the upstream docs. I
> have worked on the problem with the patch, which works down to OpenSSL
> 0.9.8, and should fix your issue. This is based on what you sent
> previously, except that I was not able to apply what was sent, so I
> reworked the whole. Alessandro, does this fix your problems? I would
> like to apply that down to v10 where SCRAM has been introduced.

I recommend letting this bake in the master branch for a while. There
are a lot weirdly patched and alternative OpenSSL versions out there
that defy any documentation.

Of course, we should also see if this actually fixes the reported problem.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Paquier 2018-09-11 22:24:24 Re: scram-sha-256 authentication broken in FIPS mode
Previous Message Geoff Winkless 2018-09-11 14:22:03 Re: Why order by column not using index with distinct keyword in select clause?