This is a review of "Password identifiers, protocol aging and SCRAM
Contents & Purpose
There was a discussion dedicated to SCRAM:
On Wed, Mar 2, 2016 at 5:43 PM, Valery Popov wrote:
>>> 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
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.
On Wed, Mar 2, 2016 at 4:05 AM, Dmitry Dolgov <9erthali...@gmail.com> wrote:
Thanks for the review.
> The default value contains "scram". Shouldn't be here also:
>>Specifies a comma-separated list of supported password formats by
>>the server. Supported formats are
On 1 March 2016 at 06:34, Michael Paquier wrote:
> On Mon, Feb 29, 2016 at 8:43 PM, Valery Popov
> > vpopov@vpopov-Ubuntu:~/Projects/pwdtest/postgresql$ git branch
> Thanks for the input!
On Mon, Feb 29, 2016 at 8:43 PM, Valery Popov wrote:
> vpopov@vpopov-Ubuntu:~/Projects/pwdtest/postgresql$ git branch
Thanks for the input!
> 0001-Add-facility-to-store-multiple-password-verifiers.patch:2547: trailing
> warning: 1 line adds whitespace
23.02.2016 10:17, Michael Paquier пишет:
Attached is a set of patches implementing a couple of things that have
been discussed, so let's roll in.
Those 4 patches are aimed at putting in-core basics for the concept I
call password protocol aging, which is a way to allow multiple