| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | 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-27 21:52:15 |
| Message-ID: | b0e5aebb-3d4a-4dd2-93e7-6c5e2f3ba033@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Melanie Plageman | 2023-12-27 22:16:17 | Add LSN <-> time conversion functionality |
| Previous Message | Dagfinn Ilmari Mannsåker | 2023-12-27 21:51:26 | Assorted typo fixes |