Re: [REVIEW]: Password identifiers, protocol aging and SCRAM protocol

From: Valery Popov <v(dot)popov(at)postgrespro(dot)ru>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Dmitry Dolgov <9erthalion6(at)gmail(dot)com>
Cc: PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [REVIEW]: Password identifiers, protocol aging and SCRAM protocol
Date: 2016-03-02 08:43:23
Message-ID: 56D6A7AB.50306@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> <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>-- Regards, Valery Popov
Postgres Professional http://www.postgrespro.com The Russian Postgres
Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2016-03-02 09:05:19 Re: Issue with NULLS LAST, with postgres_fdw sort pushdown
Previous Message Kyotaro HORIGUCHI 2016-03-02 08:33:25 Re: Freeze avoidance of very large table.