pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Heikki Linnakangas <hlinnaka@iki.fi>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Julian Markwort <julian.markwort@uni-muenster.de>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: David Steele <david@pgmasters.net>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Cc: Valery Popov <v.popov@postgrespro.ru>
Subject: Re: Password identifiers, protocol aging and SCRAM protocol
Date: Sun, 3 Jul 2016 17:34:00 -0400
Message-ID: <84a8f3d6-333d-1606-ac66-259a10898e6c@2ndquadrant.com> (raw )
In-Reply-To: <753ff453-b6b6-56c6-9b73-8190731a5f87@iki.fi >
References: <CAB7nPqSMXU35g=W9X74HVeQp0uvgJxvYOuA4A-A3M+0wfEBv-w@mail.gmail.com >
<CAB7nPqTssJpBUZ8g9oUTPJ6RPLCZYFtPypzdYgHL1gtuskxwkw@mail.gmail.com >
<56EAF483.3030307@pgmasters.net >
<CAB7nPqTkoC4NLyyivz2=usUOo47iZnS+2e14nkmVKM3P8hWqwA@mail.gmail.com >
<CA+TgmoYeui5crJyn4xxCZLUnxjtcZ1bzzF9-YN9NOQ-wr2f_uw@mail.gmail.com >
<20160318181252.GA3127@tamriel.snowman.net >
<CA+TgmobPNhnnMjOwG6s7zFznzh7g3JsUkLFvQBnh4+Ua++_6qA@mail.gmail.com >
<CAB7nPqRChAg7fUMZJ3FJpVjzaq9yYDPzxtBLOHVMnwjDAgyx=w@mail.gmail.com >
<CA+TgmoY790rphHBogXMbTG6MzSeNdoxdBXebEkAet9ZpZ8gvtw@mail.gmail.com >
<CAB7nPqSHTF3pSz1_rQFE74gGUg8dpyP2kNGiw-Eu_DHEoi+okA@mail.gmail.com >
<CABUevExLdymjo_vDCvE4WCsHdp-tjpTMOJgwyQ23y-gFoCAVrQ@mail.gmail.com >
<56FAB0D3.6070003@uni-muenster.de >
<CAB7nPqSjwsY4hYaKh-w4u0EB+YaxnQi7R63J9KgwcRe+RbaXTA@mail.gmail.com >
<CA+TgmoahM22VCuNtM-33WE56WCQ59o_jbF0A3VChdwZ4paaesw@mail.gmail.com >
<CAB7nPqSSzWEc-7S2VhenA36xTFa2mDxmb4erUApca8vc6bG9iw@mail.gmail.com >
<753ff453-b6b6-56c6-9b73-8190731a5f87@iki.fi >
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
On 7/2/16 3:54 PM, Heikki Linnakangas wrote:
> In related news, RFC 7677 that describes a new SCRAM-SHA-256
> authentication mechanism, was published in November 2015. It's identical
> to SCRAM-SHA-1, which is what this patch set implements, except that
> SHA-1 has been replaced with SHA-256. Perhaps we should forget about
> SCRAM-SHA-1 and jump straight to SCRAM-SHA-256.
I think a global change from SHA-1 to SHA-256 is in the air already, so
if we're going to release something brand new in 2017 or so, it should
be SHA-256.
I suspect this would be a relatively simple change, so I wouldn't mind
seeing a SHA-1-based variant in CF1 to get things rolling.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
view thread (149+ messages) latest in thread
Message-ID: <84a8f3d6-333d-1606-ac66-259a10898e6c@2ndquadrant.com>
Permalink: ../84a8f3d6-333d-1606-ac66-259a10898e6c@2ndquadrant.com/
Also on: postgresql.org/message-id/84a8f3d6-333d-1606-ac66-259a10898e6c@2ndquadrant.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, hlinnaka@iki.fi, michael.paquier@gmail.com, robertmhaas@gmail.com, julian.markwort@uni-muenster.de, magnus@hagander.net, sfrost@snowman.net, david@pgmasters.net, v.popov@postgrespro.ru
Subject: Re: Password identifiers, protocol aging and SCRAM protocol
In-Reply-To: <84a8f3d6-333d-1606-ac66-259a10898e6c@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox