Re: [REVIEW]: Password identifiers, protocol aging and SCRAM protocol - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [REVIEW]: Password identifiers, protocol aging and SCRAM protocol
Date
Msg-id CAB7nPqQxdgQRien=dCJuCPfHvPhsMTkvdU8S3vvNn5+9OAZj8w@mail.gmail.com
Whole thread Raw
In response to Re: [REVIEW]: Password identifiers, protocol aging and SCRAM protocol  (Valery Popov <v.popov@postgrespro.ru>)
Responses Re: [REVIEW]: Password identifiers, protocol aging and SCRAM protocol  (Valery Popov <v.popov@postgrespro.ru>)
List pgsql-hackers
On Wed, Mar 2, 2016 at 5:43 PM, Valery Popov <v.popov@postgrespro.ru> wrote:
>
>>>        <para>
>>>         <varname>db_user_namespace</> causes the client's and
>>>         server's user name representation to differ.
>>>         Authentication checks are always done with the server's user name
>>>         so authentication methods must be configured for the
>>>         server's user name, not the client's.  Because
>>>         <literal>md5</> uses the user name as salt on both the
>>>         client and server, <literal>md5</> cannot be used with
>>>         <varname>db_user_namespace</>.
>>>        </para>
>
> Also in doc/src/sgml/ref/create_role.sgml is should be instead of
>       <term>PASSWORD VERIFIERS ( <replaceable
> class="PARAMETER">verifier_type</replaceable> = '<replaceable
> class="PARAMETER">password</replaceable>'</term>
> like this
>       <term><literal>PASSWORD VERIFIERS</> ( <replaceable
> class="PARAMETER">verifier_type</replaceable> = '<replaceable
> class="PARAMETER">password</replaceable>'</term>

So the <literal> markup is missing. Thanks. I am taking note of it.
-- 
Michael



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [NOVICE] WHERE clause not used when index is used
Next
From: Magnus Hagander
Date:
Subject: Re: Commitfest Bug (was: Re: Reusing abbreviated keys during second pass of ordered [set] aggregates)