From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
Cc: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Maximum password length |
Date: | 2018-10-12 21:23:38 |
Message-ID: | 20181012212338.GW4184@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Bossart, Nathan (bossartn(at)amazon(dot)com) wrote:
> On 10/12/18, 4:04 PM, "Isaac Morland" <isaac(dot)morland(at)gmail(dot)com> wrote:
> > I agree there should be a specific limit that is the same in libpq,
> > on the server, and in the protocol. Maybe 128 characters, to get a
> > nice round number? This is still way longer than the 32-byte SHA 256
> > hash. Or 64, which is still plenty but doesn't involve extending the
> > current character buffer size to a longer value while still hugely
> > exceeding the amount of information in the hash.
>
> My main motivation for suggesting the increase to 8k is to provide
> flexibility for alternative authentication methods like LDAP, RADIUS,
> PAM, and BSD.
Specific use-cases here would be better than hand-waving at "these other
things." Last I checked, all of those work with what we've got today
and I don't recall hearing complaints about them not working due to this
limit.
Thanks!
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2018-10-12 21:46:17 | Re: pgsql: Add TAP tests for pg_verify_checksums |
Previous Message | Tom Lane | 2018-10-12 21:22:50 | Re: Maximum password length |