public inbox for [email protected]  

help / color / mirror / Atom feed

From: Peter Eisentraut <[email protected]>
To: Bruce Momjian <[email protected]>
To: Robert Haas <[email protected]>
Cc: Stephen Frost <[email protected]>
Cc: Michael Paquier <[email protected]>
Cc: PostgreSQL mailing lists <[email protected]>
Subject: Re: [HACKERS] Changing references of password encryption to hashing
Date: Wed, 27 Dec 2023 22:52:15 +0100
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <CAB7nPqR82_57C8O1+z-bUChhHpdjMec_omLfKwYdjAFjjcrBWg@mail.gmail.com>
	<[email protected]>
	<ZWX/[email protected]>
	<CA+Tgmoa44Q+rajT2FC2S7R3-hfh0xXTEa+qLzdYD0Gh9DPoX3Q@mail.gmail.com>
	<[email protected]>

On 27.12.23 02:04, Bruce Momjian wrote:
> I did_not_  change the user API, so CREATE/ALTER ROLE still uses
> [ENCRYPTED] PASSWORD, the GUC is still called password_encryption, and
> the libpq function is still called PQencryptPasswordConn().  This makes
> the user interface confusing since the API uses "encryption" but the
> text calls it "hashing".  Is there support for renaming the API to use
> "hash" and keeping "encrypt" for backward compatiblity.

Yeah, this is clearly confusing.  I think we should just leave it alone. 
  Some gentle rewording here and there to clarify things might be 
appropriate (but the text already uses hashing on some occasions), but 
the blanket replacement does not make things better, I think.

view thread (4+ messages)  latest in thread

reply

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [HACKERS] Changing references of password encryption to hashing
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox