| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Changing references of password encryption to hashing |
| Date: | 2023-12-29 17:46:14 |
| Message-ID: | ZY8F5nyZmTXj56-x@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Only you can decide what is important to you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2023-12-29 17:55:52 | Re: [PATCH] plpython function causes server panic |
| Previous Message | Heikki Linnakangas | 2023-12-29 17:38:47 | Re: Avoid computing ORDER BY junk columns unnecessarily |