From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, Aleksander Alekseev <aleksander(at)timescale(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PATCH: warn about, and deprecate, clear text passwords |
Date: | 2025-03-03 18:54:59 |
Message-ID: | CA+TgmoY1=af8d5T47wAW__vfaNXUY-QOP00bd_=Rzg=NPcNxJQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Mar 3, 2025 at 1:47 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > I wonder if we could drum up some support for not including any
> > version of the password (even encrypted) in the query string. For
> > instance, let's say that to change your password you have to use the
> > new CHANGE PASSWORD command which can only be used at top level (not
> > inside PL code or whatever) and always takes a single parameter that
> > must be supplied via the extended query protocol.
>
> How would pg_dumpall cope with transferring passwords then?
>
> I could see insisting that plain-text passwords be supplied only
> that way. But removing the ability to have encrypted passwords
> in-line seems like a serious operational problem with little benefit.
Oh, good point. I don't know. I just have heard a LOT of complaining
about passwords showing up in the log, and I'm not sure insisting that
they have to all be encrypted is going to make all of the complaining
stop.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Sabino Mullane | 2025-03-03 19:00:35 | Re: Statistics Import and Export |
Previous Message | Tom Lane | 2025-03-03 18:47:27 | Re: PATCH: warn about, and deprecate, clear text passwords |