Message-ID: <8fad4f72-920f-d74c-0ddc-dd5c4d401c60@gmail.com>
Date: Wed, 15 Feb 2023 15:29:43 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101
 Thunderbird/102.7.2
Subject: Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored
 with openssl 1.1.1 with builtin decrypter one
Content-Language: it
To: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-bugs@lists.postgresql.org
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>
From: "agharta82@gmail.com" <agharta82@gmail.com>
Disposition-Notification-To: "agharta82@gmail.com" <agharta82@gmail.com>
In-Reply-To: <CDC0431F-6CD4-4B7A-9D52-D59E87050E32@yesql.se>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/8fad4f72-920f-d74c-0ddc-dd5c4d401c60%40gmail.com>
Precedence: bulk

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
>