| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Noah Misch <noah(at)leadboat(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, magnus(at)hagander(dot)net, robertmhaas(at)gmail(dot)com |
| Subject: | Re: SCRAM authentication, take three |
| Date: | 2017-04-11 01:52:21 |
| Message-ID: | f7cc4517-638b-6b63-84e8-f4892a814573@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/10/17 04:27, Heikki Linnakangas wrote:
> One thing to consider is that we just made the decision that "md5"
> actually means "md5 or scram-sha-256". Extrapolating from that, I think
> we'll want "scram-sha-256" to mean "scram-sha-256 or scram-sha-256-plus"
> (i.e. the channel-bonding variant) in the future. And if we get support
> for scram-sha-512, "scram-sha-256" would presumably allow that too.
But how would you choose between scram-sha-256-plus and scram-sha-512?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-04-11 02:08:28 | Re: SUBSCRIPTIONS and pg_upgrade |
| Previous Message | David G. Johnston | 2017-04-11 01:48:16 | Re: Ongoing issues with representation of empty arrays |