Re: BUG #19702: decode() accepts Base64 payload after terminal padding

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: shihao zhong <zhong950419(at)gmail(dot)com>, imchifan(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19702: decode() accepts Base64 payload after terminal padding
Date: 2026-11-10 09:23:54
Message-ID: DA51DA42-E481-48CB-B0F0-B5438EABEEEC@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 9 Nov 2026, at 23:43, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:

> Thank you for taking care of it. I was also reviewing the patches and
> was about to send LGTM.

+1

> While I agree that we don't backpatch it to v18 or older, I think it
> (or at least the base64url part) should go into v19 as well. v19 is
> still in RC and base64url is new in v19, so there are no existing
> users relying on the current behavior, and it would be better to make
> base64url and base32hex consistent before the release.

That's a good point, I'll prepare a backpatch for 19 for the relevant portions.

--
Daniel Gustafsson

In response to

Browse pgsql-bugs by date

  From Date Subject
Previous Message PG Bug reporting form 2026-11-10 09:21:43 BUG #19860: LDAP authentication fails for non-ASCII passwords and usernames on Windows (UTF-8 bytes passed to th