On 2019-10-29 15:34, Tom Lane wrote:
Peter Eisentraut writes:
On 2019-10-28 14:45, Tom Lane wrote:
Kyotaro Horiguchi writes:
In think one of the reasons for the coding is the fact that *pw is
described to be placed in the static area, which can be overwritten by
succeeding calls to getpw*()
Peter Eisentraut writes:
> On 2019-10-28 14:45, Tom Lane wrote:
>> Kyotaro Horiguchi writes:
>>> In think one of the reasons for the coding is the fact that *pw is
>>> described to be placed in the static area, which can be overwritten by
>>> succeeding calls to getpw*() functions.
>> Good point
On 2019-10-28 14:45, Tom Lane wrote:
Kyotaro Horiguchi writes:
At Sat, 26 Oct 2019 08:55:03 +0200, Peter Eisentraut
wrote in
IDENT_USERNAME_MAX is the maximum length of the information returned
by an ident server, per RFC 1413. Using it as the buffer size in peer
authentication is inappropr
Kyotaro Horiguchi writes:
> At Sat, 26 Oct 2019 08:55:03 +0200, Peter Eisentraut
> wrote in
>> IDENT_USERNAME_MAX is the maximum length of the information returned
>> by an ident server, per RFC 1413. Using it as the buffer size in peer
>> authentication is inappropriate. It was done here bec
Hello.
At Sat, 26 Oct 2019 08:55:03 +0200, Peter Eisentraut
wrote in
> IDENT_USERNAME_MAX is the maximum length of the information returned
> by an ident server, per RFC 1413. Using it as the buffer size in peer
> authentication is inappropriate. It was done here because of the
> historical r
, Training & Services
From 1fed5a94b801471cb380e447b5f0b924b3819be6 Mon Sep 17 00:00:00 2001
From: Peter Eisentraut
Date: Sat, 26 Oct 2019 08:48:28 +0200
Subject: [PATCH] Remove one use of IDENT_USERNAME_MAX
IDENT_USERNAME_MAX is the maximum length of the information returned
by an ident server, per
