From: agharta82@gmail.com <agharta82@gmail.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one
Date: Wed, 15 Feb 2023 15:29:43 +0100
Message-ID: <8fad4f72-920f-d74c-0ddc-dd5c4d401c60@gmail.com> (raw)
In-Reply-To: <CDC0431F-6CD4-4B7A-9D52-D59E87050E32@yesql.se>
References: <17796-a35e6387be088a9b@postgresql.org>
<AE5DB690-E8EE-4E4C-917D-10ED65418459@yesql.se>
<b65823d5-39e5-2fd1-7c91-ae3f1fa94e22@gmail.com>
<CDC0431F-6CD4-4B7A-9D52-D59E87050E32@yesql.se>
Il 15/02/23 15:09, Daniel Gustafsson ha scritto:
>> On 15 Feb 2023, at 15:03, agharta82@gmail.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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: agharta82@gmail.com, daniel@yesql.se, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one
In-Reply-To: <8fad4f72-920f-d74c-0ddc-dd5c4d401c60@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox