Re: md5_password_warnings for password auth with MD5-encrypted passwords

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: md5_password_warnings for password auth with MD5-encrypted passwords
Date: 2026-06-30 00:38:17
Message-ID: CAHGQGwEtTZNBeBPNe4gOSDnsH-1ez5qLE-=NhDtAuerJvwGJAw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Jun 29, 2026 at 12:00 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> > I'm fine with expanding the warnings to "password" auth. Something else I
> > considered is whether we should warn if a role with an MD5 password is
> > authenticated without using the password. I ultimately decided against
> > that, but we could expand it there, too.

Agreed with that decision, i.e., I don't think we should warn in those cases
(e.g., a role with an MD5 password being authenticated via trust). The MD5
verifier isn't used for authentication there, and emitting the warning would
require an extra lookup of the role's password solely to generate the warning.
That seems like unnecessary overhead.

> FWIW, emitting a WARNING for the "password" case would make more
> people aware that they're doing something wrong. Folks having the
> idea to allow plain password authentication should be hopefully next
> to nothing these days (mostly self-managed), but the more warned the
> less potential pain when this gets removed.

+1

> In short, I think that Fujii-san's patch is a good thing to have.

Thanks! So I'm thinking to commit the patch.

Regards,

--
Fujii Masao

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Corey Huinker 2026-06-30 00:51:34 Re: statatt_build_stavalues->LOCAL_FCINFO wrong number
Previous Message Bruce Momjian 2026-06-30 00:09:58 Re: Get rid of "Section.N.N.N" on DOCs