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-10 11:39:24
Message-ID: 6B9D968C-3411-4717-AAB6-364C7EFEEA9E@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 9 Sep 2024, at 23:21, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
>
>> 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.

Pushed, thanks!

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2024-09-10 12:02:34 Re: Proposal to Enable/Disable Index using ALTER INDEX
Previous Message Nazir Bilal Yavuz 2024-09-10 11:35:46 Re: Use read streams in pg_visibility