Re: [HACKERS] Changing references of password encryption to hashing - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] Changing references of password encryption to hashing
Date
Msg-id ZY8F5nyZmTXj56-x@momjian.us
Whole thread Raw
In response to Re: [HACKERS] Changing references of password encryption to hashing  (Peter Eisentraut <peter@eisentraut.org>)
List pgsql-hackers
On Wed, Dec 27, 2023 at 10:52:15PM +0100, Peter Eisentraut wrote:
> 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.

Seeing no more replies, I will abandon this improvement idea.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  Only you can decide what is important to you.



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Avoid computing ORDER BY junk columns unnecessarily
Next
From: Tom Lane
Date:
Subject: Re: [PATCH] plpython function causes server panic