pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Nathan Bossart <nathandbossart@gmail.com>
To: Andreas Karlsson <andreas@proxel.se>
Cc: pgsql-hackers@postgresql.org
Subject: Re: add warning upon successful md5 password auth
Date: Fri, 13 Feb 2026 11:26:26 -0600
Message-ID: <aY9ewvQr4PBCVe0e@nathan> (raw)
In-Reply-To: <0731e3d8-3d13-4539-addc-a2c13a8b1b14@proxel.se>
References: <aYzeAYEbodkkg5e-@nathan>
	<0731e3d8-3d13-4539-addc-a2c13a8b1b14@proxel.se>

On Fri, Feb 13, 2026 at 06:04:14AM +0100, Andreas Karlsson wrote:
> 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.

FWIW if users are really annoyed with these warnings, they can disable them
by setting md5_password_warnings to off.  But I think we really ought to do
something like $subject before we completely remove MD5 password support.

-- 
nathan





view thread (10+ messages)  latest in thread

Message-ID: <aY9ewvQr4PBCVe0e@nathan>
Permalink:  ../aY9ewvQr4PBCVe0e@nathan/
Also on:    postgresql.org/message-id/aY9ewvQr4PBCVe0e@nathan

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: nathandbossart@gmail.com, andreas@proxel.se
  Subject: Re: add warning upon successful md5 password auth
  In-Reply-To: <aY9ewvQr4PBCVe0e@nathan>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox