From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Mladen Gogala <gogala.mladen@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: Password authorization
Date: Fri, 21 Jan 2022 15:18:50 +0100
Message-ID: <5e4ed7296493684b40a5fa7fb009edf92f5e9ade.camel@cybertec.at> (raw)
In-Reply-To: <d4fd7ed1-5dd5-7a1b-0df1-5df80cc3f0cc@gmail.com>
References: <CALfOM6KtjqpO5pYgmpUmDScJMeftv9r509HfYLo2b8gebviL3g@mail.gmail.com>
<f0455f10526a0463c9e99fc803b6e5ebfd518894.camel@cybertec.at>
<d4fd7ed1-5dd5-7a1b-0df1-5df80cc3f0cc@gmail.com>
On Fri, 2022-01-21 at 09:10 -0500, Mladen Gogala wrote:
> On 1/20/22 09:25, Laurenz Albe wrote:
>
> > It is not quite clear what you mean, but I assume you want password complexity rules,
> > and you want to force users to change their password after a while.
> >
> > You cannot do any of that with passwords in the database; the best you can
> > do is set an expiration time for the user's ability to log in.
> Actually, you can. There is the standard "passwordcheck" module described in the documentation:
> https://www.postgresql.org/docs/current/passwordcheck.html
> You would have to do some C programming, but it's very possible.
That is no solution, because it cannot check hashed passwords
(except with cracklib). I wrote it.
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: laurenz.albe@cybertec.at, gogala.mladen@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: Password authorization
In-Reply-To: <5e4ed7296493684b40a5fa7fb009edf92f5e9ade.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox