From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nicholas Chammas <nicholas.chammas@gmail.com>
cc: pgsql-admin@lists.postgresql.org
Subject: Re: Amazon RDS auth tokens in .pgpass
In-reply-to: 
 <CAOhmDzejZ2N3kNL42crFNViPVw7jtzV2Pz3tcmTmONUqNZS1AQ@mail.gmail.com>
References: 
 <CAOhmDze1nqG2vfegpSsTFCgaiFRsqgjO6yLsbmhroz2zGmJHog@mail.gmail.com>
 <4119486.1598897040@sss.pgh.pa.us>
 <CAOhmDzejZ2N3kNL42crFNViPVw7jtzV2Pz3tcmTmONUqNZS1AQ@mail.gmail.com>
Comments: In-reply-to Nicholas Chammas <nicholas.chammas@gmail.com>
	message dated "Mon, 31 Aug 2020 15:12:01 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <142973.1598984710.1@sss.pgh.pa.us>
Date: Tue, 01 Sep 2020 14:25:10 -0400
Message-ID: <142974.1598984710@sss.pgh.pa.us>
Precedence: bulk

Nicholas Chammas <nicholas.chammas@gmail.com> writes:
> On Mon, Aug 31, 2020 at 2:04 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> Looking at the source code, there's a hard-wired restriction that lines of
>> .pgpass can't be more than 320 characters long (well, NAMEDATALEN*5, but
>> very few builds don't have NAMEDATALEN=64).  I see that somebody very
>> recently added code to make libpq print a warning for overlength lines,
>> but I wonder why they didn't just, um, remove the restriction.  We had
>> not previously heard of a use-case for passwords with hundreds of
>> characters in them, but I guess we need to cope.

> Just FYI, the auth tokens generated by Amazon RDS appear to be 796 bytes
> long.

Thanks.  I've pushed a fix to remove libpq's undocumented restriction
on the length of a .pgpass line.  It will be in November's releases.

			regards, tom lane