Re: BUG #19714: pgcrypto pgp_sym_encrypt accepts nonnumeric s2k-mode as mode 0

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: Sho Ito <i(dot)sho(dot)0628(at)gmail(dot)com>, imchifan(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19714: pgcrypto pgp_sym_encrypt accepts nonnumeric s2k-mode as mode 0
Date: 2026-11-12 12:44:57
Message-ID: CC2E9B00-E236-429D-8A76-7DCCCF63ADAB@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 11 Nov 2026, at 02:03, shihao zhong <zhong950419(at)gmail(dot)com> wrote:

> Thanks for v2. expect-s2k-mode now goes through PARSE_INT_AS_BOOL, so
> the existing expect-s2k-mode=3 tests in pgp-encrypt fail.

Yes, fixed in the attached.

I also expanded the check for compression which allows the undocumented (and
not working) bzip2 option now as well which the previous coding did. Attached
is what I have lined up for later today.

--
Daniel Gustafsson

Attachment Content-Type Size
v3-0001-pgcrypto-reject-invalid-PGP-options.patch application/octet-stream 8.9 KB

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Konstantin Knizhnik 2026-11-12 12:47:34 Re: BUG #19519: REPACK can fail due to missing chunk for toast value
Previous Message PG Bug reporting form 2026-11-12 12:41:55 BUG #19896: transaction_timeout misbehaves after ROLLBACK TO SAVEPOINT and after errors