Re: Add a warning message when using unencrypted passwords

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
Cc: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add a warning message when using unencrypted passwords
Date: 2024-12-09 13:40:09
Message-ID: 3493E259-D4AF-4105-A9D7-1CBFD579E0FB@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 9 Dec 2024, at 14:26, Greg Sabino Mullane <htamfids(at)gmail(dot)com> wrote:

> -1 to throwing an ERROR - that's not really an error, and not our call to make, so a WARNING is sufficient.

Agreed, regardless of how bad it's considered, it's not an error. There are
many ways sensitive data can end up in the logs and offering the impression
there is a safety switch offers a false sense of security.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Melanie Plageman 2024-12-09 14:01:27 Re: Wrong results with right-semi-joins
Previous Message Alexander Borisov 2024-12-09 13:39:03 Re: Proposal to add a new URL data type.