Re: Non-compliant SASLprep implementation for ASCII characters

Michael Paquier <michael@paquier.xyz>

View thread

From: Michael Paquier <michael@paquier.xyz>

To: Alexander Lakhin <exclusion@gmail.com>

Cc: John Naylor <johncnaylorls@gmail.com>, Postgres hackers <pgsql-hackers@lists.postgresql.org>

Date: 2026-04-12T11:47:10Z

Lists: pgsql-hackers

Attachments

saslprep-test.patch (text/plain) patch

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

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

test_saslprep: Fix issue with copy of input bytea
- 5d35531af184 19 (unreleased) landed
Make implementation of SASLprep compliant for ASCII characters
- 3d10ece612f5 19 (unreleased) landed
test_saslprep: Test module for SASLprep()
- aa73838a5c94 19 (unreleased) landed