Re: pg_upgrade: warn about roles with md5 passwords - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: pg_upgrade: warn about roles with md5 passwords
Date
Msg-id aD3ZgHLMu58pAUpy@nathan
Whole thread Raw
In response to Re: pg_upgrade: warn about roles with md5 passwords  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-hackers
On Mon, Jun 02, 2025 at 09:45:55AM -0700, Jeff Davis wrote:
> On Mon, 2025-06-02 at 10:32 -0500, Nathan Bossart wrote:
>> The one thing I don't like about this check is that it's probably not
>> great
>> from a security standpoint to effectively announce which roles have
>> MD5
>> passwords.
> 
> Do you have a specific concern, or is that more of a general concern?

General.

>> One other thing I noticed is that checks that only emit warnings,
>> like
>> check_for_unicode_update(), require using --retain in order to see
>> the
>> generated report file.
> 
> Should we automatically retain files associated with warnings, or copy
> them to a different location?

That seems worth considering.  Another option could be to just document
that files generated for warnings will be lost without --retain.  WDYT?

-- 
nathan



pgsql-hackers by date:

Previous
From: Alena Rybakina
Date:
Subject: Re: Vacuum statistics
Next
From: Tom Lane
Date:
Subject: Re: tighten generic_option_name, or store more carefully in catalog?