From: Michael Paquier <michael@paquier.xyz>
To: Jonathan S. Katz <jkatz@postgresql.org>
Cc: sebihoorens@gmail.com
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: scram-sha-256 authentication
Date: Wed, 6 Jan 2021 10:57:46 +0900
Message-ID: <X/UZGjUFo4BZWMdB@paquier.xyz> (raw)
In-Reply-To: <0707a341-0c2e-3fe4-fe65-607bea83aced@postgresql.org>
References: <160977988728.3264.12890569380100648489@wrigleys.postgresql.org>
<0707a341-0c2e-3fe4-fe65-607bea83aced@postgresql.org>
On Tue, Jan 05, 2021 at 09:12:58AM -0500, Jonathan S. Katz wrote:
> I am not sure what your end goal is, but there are a few ways to create
> the hashed SCRAM verifier:
>
> - Using the \password flag in "psql"
> - Using one of the connection drivers that interfaces with libpq's
> PQencryptPasswordConn function[2]
> - Some driver's handle the password hashing independently
Another thing to be careful about is the value of password_encryption
in postgresql.conf. The default has been changed to scram-sha-256 in
c7eab0e, meaning that this change will be available in Postgres 14~.
But if your environment is using the default configuration of 11, that
may be set to "md5".
--
Michael
Attachments:
signature.asc (application/pgp-signature, 832B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: michael@paquier.xyz, jkatz@postgresql.org, sebihoorens@gmail.com, pgsql-docs@lists.postgresql.org
Subject: Re: scram-sha-256 authentication
In-Reply-To: <X/UZGjUFo4BZWMdB@paquier.xyz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox