Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one

From: "agharta82(at)gmail(dot)com" <agharta82(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one
Date: 2023-02-15 14:29:43
Message-ID: 8fad4f72-920f-d74c-0ddc-dd5c4d401c60@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Il 15/02/23 15:09, Daniel Gustafsson ha scritto:

>> On 15 Feb 2023, at 15:03, agharta82(at)gmail(dot)com wrote:
>> Meanwhile, to solve the case:
>>
>> • in Linux is quite simple (but insecure), enable legacy ciphers.
> Enabling the legacy ciphers provider isn't insecure per se, the use of said
> ciphers might be insecure but having the code loaded isn't.

True, and wise.

>
>> • in Windows....uh....i've not found how to solve it because (if i am not wrong) PG 15 is built with openssl 3 internally and i don't known how to enable legacy mode in it.
> I don't know Windows very well, but there should be an OPENSSLDIR set and in
> there one can change the openssl conf file just like on Linux AFAIK. It should
> be reasonably similar to on Linux.

Ok, I take a look.

Thanks,

Agharta

>
> --
> Daniel Gustafsson
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2023-02-15 19:42:24 Re: BUG #17792: MERGE uses uninitialized pointer and crashes when target tuple is updated concurrently
Previous Message Daniel Gustafsson 2023-02-15 14:09:28 Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one