Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.80.0.2.43\))
Subject: Re: Query on User account password change details
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: <4e87a433-531f-d108-4ef6-0c54ba44f587@gmail.com>
Date: Fri, 7 May 2021 06:30:43 -0600
Cc: pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <DFC3EF54-3AA9-468A-9537-431970DE1B3A@elevated-dev.com>
References: 
 <CAPOO3u4cxoCmJsXJaMHCLavecb-Bc77=qh=dfQN+bbYJ6gneWA@mail.gmail.com>
 <90B6B3A1-BB95-4D69-99EF-D86C0A859431@jakobs.com>
 <4e87a433-531f-d108-4ef6-0c54ba44f587@gmail.com>
To: Ron <ronljohnsonjr@gmail.com>
Archived-At: 
 <https://www.postgresql.org/message-id/DFC3EF54-3AA9-468A-9537-431970DE1B3A%40elevated-dev.com>
Precedence: bulk

> On May 6, 2021, at 11:40 PM, Ron <ronljohnsonjr@gmail.com> wrote:
>=20
> Comments like this are indicative of someone who's never been through =
an external audit.

While maybe true, the point stands that even the original source of the =
requirement has admitted it's a bad idea, and standards bodies are =
dropping it. So, unlike many other things we might consider pointless, =
with this one, you have the kind of defense that might work in an audit.=