Re: add warning upon successful md5 password auth - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: add warning upon successful md5 password auth
Date
Msg-id 0731e3d8-3d13-4539-addc-a2c13a8b1b14@proxel.se
Whole thread Raw
In response to add warning upon successful md5 password auth  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: add warning upon successful md5 password auth
List pgsql-hackers
On 2/11/26 8:52 PM, Nathan Bossart wrote:
> Since I just added a "connection warnings" infrastructure in commit
> 1d92e0c2cc, I thought it might be a good time to revisit this idea.
> Attached is an updated patch.  I'm not sure this is v19 material.  It could
> make sense to wait until v20 or something.  But I figured it was worth at
> least having the discussion.
The patch looks good and I think it would make sense to merge it in 19, 
why wait for 20? But the main question I see is if this is too noisy or 
not. Some applications connected to PostgreSQL quite a lot and I am sure 
we would make some users unhappy so I am not fully on board with this 
patch. But on the other hand we have way too many people who still use 
md5 and we really should push them towards using scram.

Andreas




pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: 64-bit wait_event and introduction of 32-bit wait_event_arg
Next
From: Michael Paquier
Date:
Subject: Re: Report bytes and transactions actually sent downtream