From: | Nicholas Chammas <nicholas(dot)chammas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Amazon RDS auth tokens in .pgpass |
Date: | 2020-09-01 22:18:14 |
Message-ID: | CAOhmDzeTBY3Ge8nsdOKLUd21Y+ZVaAHTxSXJ9U6dcLHtWr32qw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Thanks Tom. It looks like this is the commit corresponding to your fix:
https://github.com/postgres/postgres/commit/b55b4dad99e99d5306744a4e8ef8021fa3a922e4
On Tue, Sep 1, 2020 at 2:25 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Nicholas Chammas <nicholas(dot)chammas(at)gmail(dot)com> writes:
> > On Mon, Aug 31, 2020 at 2:04 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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
>
From | Date | Subject | |
---|---|---|---|
Next Message | Sanjib Mohanty | 2020-09-02 11:46:38 | Re: Postgres Replication on a different network interface |
Previous Message | Tom Lane | 2020-09-01 18:25:10 | Re: Amazon RDS auth tokens in .pgpass |