Re: [PATCH] Fix small overread during SASLprep

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] Fix small overread during SASLprep
Date: 2024-09-09 21:21:16
Message-ID: 13AFC696-52F8-4B14-9D20-7F6C8F943D2E@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 9 Sep 2024, at 20:41, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> wrote:
>
> On Mon, Sep 9, 2024 at 11:30 AM Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>> Just to make sure I understand, this is for guarding against overreads in
>> validation of strings containing torn MB characters?
>
> Right. Our SASLprep code doesn't require/enforce UTF8-encoded inputs.

Thanks for confirming, I'll have another look in the morning and will apply
then unless there are objections.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2024-09-09 21:29:09 Re: Retire support for OpenSSL 1.1.1 due to raised API requirements
Previous Message Masahiko Sawada 2024-09-09 21:20:44 Re: Pgoutput not capturing the generated columns