| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net>, Devrim Gündüz <devrim(at)gunduz(dot)org>, Craig Ringer <craig(at)2ndquadrant(dot)com>, pgsql-pkg-yum <pgsql-pkg-yum(at)postgresql(dot)org> |
| Subject: | Re: Can we stop defaulting to 'md5'? |
| Date: | 2020-05-28 20:05:40 |
| Message-ID: | ed0f8d57-5b2c-b08f-f94b-e15e784e8cef@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-debian pgsql-pkg-yum |
On 2020-05-28 18:38, Christoph Berg wrote:
> Why do I have to decide*in pg_hba.conf* which hash algorithm is used?
> Why can't that just be "password"?
>
> The password_encryption GUC should be the only place concerned with
> that, and it should only be used for new passwords. Existing passwords
> should just continue to work.*That* would allow seamless upgrades.
You get that if you set the authentication method to "md5". (Clearly
not a very clear name, but it exists.)
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-05-28 20:08:10 | Re: Can we stop defaulting to 'md5'? |
| Previous Message | Stephen Frost | 2020-05-28 17:09:50 | Re: Can we stop defaulting to 'md5'? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2020-05-28 20:08:10 | Re: Can we stop defaulting to 'md5'? |
| Previous Message | Stephen Frost | 2020-05-28 17:09:50 | Re: Can we stop defaulting to 'md5'? |