Re: [HACKERS] SCRAM authentication, take three

Поиск
Список
Период
Сортировка
От Michael Paquier
Тема Re: [HACKERS] SCRAM authentication, take three
Дата
Msg-id CAB7nPqS1Kk0G1E+EJEEaLEWqVNt66ER_-YZQsWk=E_m=OMe44g@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] SCRAM authentication, take three  (Aleksander Alekseev <a.alekseev@postgrespro.ru>)
Ответы Re: [HACKERS] SCRAM authentication, take three  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers
On Mon, Feb 20, 2017 at 9:41 PM, Aleksander Alekseev
<a.alekseev@postgrespro.ru> wrote:
>> Speaking about flaws, it looks like there is a memory leak in
>> array_to_utf procedure - result is allocated twice.

Pushed a fix for this one on my branch.

> And a few more things I've noticed after a closer look:
>
> * build_client_first_message does not free `state->client_nonce` if
>   second malloc (for `buf`) fails
> * same for `state->client_first_message_bare`
> * ... and most other procedures declared in fe-auth-scram.c file
>   (see malloc and strdup calls)

You are visibly missing pg_fe_scram_free().

> * scram_Normalize doesn't check malloc return value

Yes, I am aware of this one. This makes the interface utterly ugly
though because an error log message needs to be handled across many
API layers. We could just assume anything returning NULL is equivalent
to an OOM and nothing else though.
-- 
Michael



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [HACKERS] Multivariate statistics and expression indexes
Следующее
От: "Ideriha, Takeshi"
Дата:
Сообщение: Re: [WIP] RE: [HACKERS] DECLARE STATEMENT setting up a connectionin ECPG