Re: Non-compliant SASLprep implementation for ASCII characters

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Alexander Lakhin <exclusion(at)gmail(dot)com>
Cc: John Naylor <johncnaylorls(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Non-compliant SASLprep implementation for ASCII characters
Date: 2026-04-12 11:47:10
Message-ID: aduGPnmDabfEKENJ@paquier.xyz
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: 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 Content-Type Size
saslprep-test.patch text/plain 611 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2026-04-12 12:33:04 Re: Small and unlikely overflow hazard in bms_next_member()
Previous Message Thomas Munro 2026-04-12 11:37:19 ISBN range table