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

From: Sho Ito <i(dot)sho(dot)0628(at)gmail(dot)com>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: 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-10 05:18:03
Message-ID: CAG7L5+6kgn+33MzEDf6PrVomWTJdxyvibuMGJQZi0UmY6ptjnA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Shihao,

I reviewed v1 patches on master with assertions enabled. All
pgcrypto regression tests pass. Without 0001, all three new cases produce
ciphertext; with it, they raise the expected error.

I found no blocking issues. Looks good to me.

This makes some inputs that work today fail, so I'd keep it to master.
> I can do back-branch versions if a committer wants it back-patched.
>

I agree with keeping this on master. Back-patching would make previously
accepted malformed integer options fail across the PGP functions.

Thanks,
Sho

--
=======================================
*Sho Ito (Sean)*

E-mail: i(dot)sho(dot)0628(at)gmail(dot)com
LinkedIn: *https://www.linkedin.com/in/sho-ito-0628/
<https://www.linkedin.com/in/sho-ito-0628/>*
GitHub: https://github.com/sean0628/
=======================================

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2026-11-10 06:10:42 Re: BUG #19849: queries fail after ANALYZE with expression stats on arrays
Previous Message shihao zhong 2026-11-10 04:35:17 Re: BUG #19841: SQL/JSON RETURNING coercion to GUC-dependent types (timestamptz etc.) is wrongly judged IMMUTABLE -