Re: CREATE/ALTER ROLE PASSWORD ('value' USING 'method') - Mailing list pgsql-hackers

From Noah Misch
Subject Re: CREATE/ALTER ROLE PASSWORD ('value' USING 'method')
Date
Msg-id 20170406053356.GB2739265@tornado.leadboat.com
Whole thread Raw
In response to Re: [HACKERS] CREATE/ALTER ROLE PASSWORD ('value' USING 'method')  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: CREATE/ALTER ROLE PASSWORD ('value' USING 'method')  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On Fri, Mar 17, 2017 at 10:10:59AM +0900, Michael Paquier wrote:
> On Fri, Mar 17, 2017 at 2:30 AM, Jeff Janes <jeff.janes@gmail.com> wrote:
> > On Thu, Mar 9, 2017 at 4:59 AM, Michael Paquier <michael.paquier@gmail.com>
> > wrote:
> >>
> >> On Thu, Mar 9, 2017 at 1:17 AM, Joe Conway <mail@joeconway.com> wrote:
> >> > On 03/07/2017 08:29 PM, Tom Lane wrote:
> >> >> Michael Paquier <michael.paquier@gmail.com> writes:
> >> >>> here is a separate thread dedicated to the following extension for
> >> >>> CREATE/ALTER ROLE: PASSWORD ('value' USING 'method').
> >> >>
> >> >> The parentheses seem weird ... do we really need those?
> >> >
> >> > +1
> >>
> >> Seeing 3 opinions in favor of that, let's do so then. I have updated
> >> the patch to not use parenthesis.
> >
> > The regression tests only exercise the CREATE ROLE...USING version, not the
> > ALTER ROLE...USING version.
> 
> Done.
> 
> > +        and <literal>plain</> for an non-hashed password.  If the password
> > +        string is already in MD5-hashed or SCRAM-hashed, then it is
> > +        stored hashed as-is.
> >
> > In the last line, I think "stored as-is" sounds better.
> 
> Okay.
> 
> > Other than that, it looks good to me.
> 
> Thanks for the review. Attached is an updated patch.

[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



pgsql-hackers by date:

Previous
From: Serge Rielau
Date:
Subject: Re: Fast Default WIP patch for discussion
Next
From: Noah Misch
Date:
Subject: Re: SCRAM authentication, take three