| From: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Password complexity/history - credcheck? |
| Date: | 2024-06-23 02:38:12 |
| Message-ID: | CANzqJaBT+LPunvKPX=88s9xPDCOyJnTHK_Tpv8K85mchLnyStA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Sat, Jun 22, 2024 at 7:28 PM Martin Goodson <kaemaril(at)googlemail(dot)com>
wrote:
> Hello.
>
> Recently our security team have wanted to apply password complexity
> checks akin to Oracle's profile mechanism to PostgreSQL, checking that a
> password hasn't been used in x months
There would have to be a pg_catalog table which stores login history.
> etc, has minimum length, x special
> characters and x numeric characters, mixed case etc.
>
Is that an after-the-fact scanner (with all the problems Tom mentioned), or
is it a client-side "check while you're typing in the *new* password"
scanner?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Muhammad Ikram | 2024-06-23 05:53:19 | Re: pg_dump restores as expected on some machines and reports duplicate keys on others |
| Previous Message | Tom Lane | 2024-06-23 00:23:08 | Re: Password complexity/history - credcheck? |