From: | Aidan Van Dyk <aidan(at)highrise(dot)ca> |
---|---|
To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Rejecting weak passwords |
Date: | 2009-10-01 14:08:57 |
Message-ID: | 20091001140857.GG586@oak.highrise.ca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> [091001 08:54]:
> In the discussion following
> http://archives.postgresql.org/pgsql-hackers/2009-09/msg01766.php
> the consensus was that a hook that allows you to implement
> a password checking routine as a module "would not hurt".
>
> So here's the patch.
> I don't think there is documentation required;
> correct me if I am wrong.
Can we have the check password hook function called in both the
plaintext/encrypted case, with a flag as to whether it's encrypted or
not?
a.
--
Aidan Van Dyk Create like a god,
aidan(at)highrise(dot)ca command like a king,
http://www.highrise.ca/ work like a slave.
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-10-01 14:09:18 | Re: Issues for named/mixed function notation patch |
Previous Message | Simon Riggs | 2009-10-01 14:07:40 | Re: Hot Standby on git |