| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, k(dot)yudhveer(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #16079: Question Regarding the BUG #16064 |
| Date: | 2019-11-16 13:29:58 |
| Message-ID: | CABUevEwMcFmXqPJgOQfnUV8XgKtWqHPiccNHY+mPJ0AfeFz-7Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
On Fri, Nov 15, 2019 at 5:42 AM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> On Tue, Oct 29, 2019 at 4:48 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > Uh, the user's credentials certainly are sent to the PG server.
>
> Perhaps we should log a warning when PostgreSQL has received a
> password over the network without SSL. Perhaps we should log another
> warning when PostgreSQL has sent a password over the network without
> SSL.
>
For the old plaintext "password" method, we log a warning when we parse the
configuration file.
Maybe we should do the same for LDAP (and RADIUS)? This seems like a better
place to put it than to log it at every time it's received?
--
Magnus Hagander
Me: https://www.hagander.net/ <http://www.hagander.net/>
Work: https://www.redpill-linpro.com/ <http://www.redpill-linpro.com/>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Manuel Rigger | 2019-11-16 22:46:02 | ALTER TABLE results in "could not find cast from 3904 to 3831" |
| Previous Message | Florian Koch | 2019-11-16 07:40:27 | Bug when creating domain from composite types |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Te | 2019-11-16 13:46:02 | Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index. |
| Previous Message | Amit Kapila | 2019-11-16 13:14:23 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |