From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: password_encryption default |
Date: | 2020-05-22 14:31:19 |
Message-ID: | CABUevExw+eFK0Hmw3n2Q9bSY3-K0joo3UyRTeXm13UJsAsVdfA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 22, 2020 at 4:13 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> > We didn't get anywhere with making the default authentication method in
> > a source build anything other than trust. But perhaps we should change
> > the default for password_encryption to nudge people to adopt SCRAM?
> > Right now, passwords are still hashed using MD5 by default, unless you
> > specify scram-sha-256 using initdb -A or similar.
>
> I think what that was waiting on was for client libraries to become
> SCRAM-ready. Do we have an idea of the state of play on that side?
>
If the summary table on the wiki at
https://wiki.postgresql.org/wiki/List_of_drivers is to be trusted, every
listed driver except Swift does.
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2020-05-22 14:37:39 | Re: Add explanations which are influenced by track_io_timing |
Previous Message | Tom Lane | 2020-05-22 14:13:24 | Re: password_encryption default |