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 aduGPnmDabfEKENJ@paquier.xyz
Whole thread Raw
In response to Re: Non-compliant SASLprep implementation for ASCII characters  (Alexander Lakhin <exclusion@gmail.com>)
Responses Re: Non-compliant SASLprep implementation for ASCII characters
List pgsql-hackers
On Sun, Apr 12, 2026 at 09:00:00AM +0300, Alexander Lakhin wrote:
> That is, strlcpy() tries to evaluate strlen() for src, which contains only
> one byte without null terminator.

Thanks for the report.  I don't know why skink is not complaining, but
I do see the failure, and I am able to fix it with the attached.  Does
it work on your side?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: ISBN range table
Next
From: David Rowley
Date:
Subject: Re: Small and unlikely overflow hazard in bms_next_member()