| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Holger Jakobs <holger(at)jakobs(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Daulat <daulat(dot)dba(at)gmail(dot)com> |
| Subject: | Re: Password complexities in Postgres v14.6 |
| Date: | 2022-12-16 19:51:36 |
| Message-ID: | CABUevEw5M0k_jzm7RYkx3vWrrzM83F0XTG8KvX-2aw5QHyLShg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Fri, Dec 16, 2022 at 7:13 PM Holger Jakobs <holger(at)jakobs(dot)com> wrote:
> (Note that this is different from the postgres setting for VALID UNTIL
> which is not about the password being valid until, it's about the entire
> user being valid until the specified time).
>
> This isn't true. It's really just the password becoming invalid and has no
> effect on other authentication methods.
>
Yeah, you're right. I got it confused with another system I've been hacking
on recently, where it's the other way around. Sorry about that!
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | raf | 2022-12-16 21:52:52 | Re: Password complexities in Postgres v14.6 |
| Previous Message | Holger Jakobs | 2022-12-16 18:13:38 | Re: Password complexities in Postgres v14.6 |