Re: Rejecting weak passwords - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Rejecting weak passwords
Date
Msg-id 603c8f070909290718rc79dde5re3282d9e5c3340cb@mail.gmail.com
Whole thread Raw
In response to Re: Rejecting weak passwords  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Rejecting weak passwords
Re: Rejecting weak passwords
List pgsql-hackers
On Tue, Sep 29, 2009 at 9:48 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> "Albe Laurenz" <laurenz.albe@wien.gv.at> writes:
>> I thought about it some more, and I think that a password checking
>> hook might still be somewhat useful even for MD5-encrypted passwords;
>> the function could guess and exclude at least that dreadful
>> all-too-frequent case of username = password.
>
> True.  You could probably even run through a moderate-size dictionary
> of weak passwords, depending on how long you're willing to make the
> user wait.  (CHECK_FOR_INTERRUPTS inside the loop would be polite ;-))

But how much value is there in that?  This whole thing seems like a
dead end to me.  No matter how long you're willing to wait, putting
the checking on the client side will let you far more validation for
the same price.

...Robert


pgsql-hackers by date:

Previous
From: Stef Walter
Date:
Subject: Re: pg_hba.conf: samehost and samenet [REVIEW]
Next
From: Peter Eisentraut
Date:
Subject: Re: Unicode UTF-8 table formatting for psql text output