| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | agharta82(at)gmail(dot)com, 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 13:25:59 |
| Message-ID: | AE5DB690-E8EE-4E4C-917D-10ED65418459@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 15 Feb 2023, at 13:15, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
> So, the problem seems that the builtin bf cipher implementation cannot
> decode the openssl one.
The internal implementation only support $2a$ hashes, are the OpenSSL hashes
$2b$ by any chance? The prefix of the hash includes this version number.
There is a patch floating around for improving blowfish support in pgcrypto but
it hasn't made its way in.
> Side note: if I enable legacy mode in openssl3 all works fine and pgcrypto
> use the openssl chiper, oblivious.
>
> Can it be solved?
If you relied on Blowfish in OpenSSL 1.1.1 then enabling the legacy provider in
OpenSSL 3.x, or downgrading to OpenSSL 1.1.1 is a solution.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | agharta82@gmail.com | 2023-02-15 14:03:49 | Re: BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one |
| Previous Message | PG Bug reporting form | 2023-02-15 12:15:53 | BUG #17796: pgcrypto undecryptable blowfish data previous stored with openssl 1.1.1 with builtin decrypter one |