Re: scram and \password

From: Noah Misch <noah(at)leadboat(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Joe Conway <mail(at)joeconway(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: scram and \password
Date: 2017-04-10 03:53:23
Message-ID: 20170410035323.GA2846583@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 05, 2017 at 08:11:25PM +0300, Heikki Linnakangas wrote:
> On 04/05/2017 06:53 PM, Robert Haas wrote:
> >On Sat, Mar 25, 2017 at 1:10 AM, Michael Paquier
> ><michael(dot)paquier(at)gmail(dot)com> wrote:
> >>On Fri, Mar 24, 2017 at 10:12 PM, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> >>>On 03/24/2017 03:02 PM, Michael Paquier wrote:
> >>>>
> >>>>In order to close this thread, I propose to reuse the patches I sent
> >>>>here to make scram_build_verifier() available to frontends:
> >>>>
> >>>>https://www.postgresql.org/message-id/CAB7nPqT4yc3u8wspYkWbG088Ndp6asMH3=Zb___Ck89CTvziYQ@mail.gmail.com
> >>>>
> >>>>And on top of it modify \password so as it generates a md5 verifier
> >>>>for pre-9.6 servers and a scram one for post-10 servers by looking at
> >>>>the backend version of the current connection. What do you think?
> >>>
> >>>Yep, sounds like a plan.
> >>
> >>And attached is a set of rebased patches, with createuser and psql's
> >>\password extended to do that.
> >
> >Heikki, are you going to do something about these? We're running out of time.
>
> Sorry I've been procrastinating. I'm on it now. (We need to do something
> about this, feature freeze or not..)

[Action required within three days. This is a generic notification.]

The above-described topic is currently a PostgreSQL 10 open item. Heikki,
since you committed the patch believed to have created it, you own this open
item. If some other commit is more relevant or if this does not belong as a
v10 open item, please let us know. Otherwise, please observe the policy on
open item ownership[1] and send a status update within three calendar days of
this message. Include a date for your subsequent status update. Testers may
discover new open items at any time, and I want to plan to get them all fixed
well in advance of shipping v10. Consequently, I will appreciate your efforts
toward speedy resolution. Thanks.

[1] https://www.postgresql.org/message-id/20170404140717.GA2675809%40tornado.leadboat.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2017-04-10 04:01:14 Re: [COMMITTERS] pgsql: Sync pg_dump and pg_dumpall output
Previous Message Ashutosh Bapat 2017-04-10 03:34:34 Re: postgres_fdw bug in 9.6