Re: Non-compliant SASLprep implementation for ASCII characters - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Non-compliant SASLprep implementation for ASCII characters
Date
Msg-id adw08BVL9DW7kY4c@paquier.xyz
Whole thread Raw
In response to Re: Non-compliant SASLprep implementation for ASCII characters  (Alexander Lakhin <exclusion@gmail.com>)
List pgsql-hackers
On Sun, Apr 12, 2026 at 04:00:00PM +0300, Alexander Lakhin wrote:
> Maybe it would make sense to find out why skink doesn't detect this (just
> in case there are or will be similar defects hiding) before pushing the
> fix...

Other fixes can also be applied separately, tackled by their
respective committers.

Saying that, I have also done an installcheck with an instance running
with valgrind, and did not spot something popping out.  The log file I
have used for the output was looking a bit weird, as if valgrind had
the idea to overwrite some portions of it, so perhaps I have missed
something.

I have fixed this one for now, thanks for the report.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: Small and unlikely overflow hazard in bms_next_member()
Next
From: Michael Paquier
Date:
Subject: Re: Fix pgstat_database.c to honor passed database OIDs