Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Daniel Gustafsson <daniel(at)yesql(dot)se>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: scram-sha-256 broken with FIPS and OpenSSL 1.0.2
Date: 2020-11-05 06:41:23
Message-ID: 20201105064123.GA14084@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 15, 2020 at 03:56:21PM +0900, Michael Paquier wrote:
> I got my hands on that, and this proves to simplify a lot things. In
> bonus, attached is a 0003 that cleans up some code in pgcrypto so as
> it uses the in-core resowner facility to handle EVP contexts.

This conflicted on HEAD with pgcrypto. Please find attached a rebased
set.
--
Michael

Attachment Content-Type Size
v3-0001-Rework-SHA2-APIs.patch text/x-diff 61.9 KB
v3-0002-Switch-sha2_openssl.c-to-use-EVP.patch text/x-diff 8.5 KB
v3-0003-Move-pgcrypto-to-use-in-core-resowner-facility-fo.patch text/x-diff 3.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message yuzuko 2020-11-05 07:03:12 Re: Autovacuum on partitioned table (autoanalyze)
Previous Message Amit Kapila 2020-11-05 06:18:24 Re: Some doubious code in pgstat.c