Re: OpenSSL 3.0.0 compatibility

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: OpenSSL 3.0.0 compatibility
Date: 2021-09-23 19:54:54
Message-ID: CA+Tgmob9K+sE9+e7=eianrvOsuxU2-EpmHKSAmuaMRpQ+ZbEHw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Sep 23, 2021 at 2:51 PM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> For the 13- backbranches we also need to backport 22e1943f1 ("pgcrypto: Check
> for error return of px_cipher_decrypt()" by Peter E) in order to avoid
> incorrect results for decrypt tests on disallowed ciphers. Does anyone have
> any concerns about applying this to backbranches?

To me it looks like it would be more concerning if we did not apply it
to back-branches.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2021-09-23 20:00:02 Re: Gather performance analysis
Previous Message Tom Lane 2021-09-23 19:53:12 Re: Re: [PATCH] Allow queries in WHEN expression of FOR EACH STATEMENT triggers