Re: Rejecting weak passwords - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Rejecting weak passwords
Date
Msg-id 9837222c0910010654n14f208fcxd05b6b431723bfb1@mail.gmail.com
Whole thread Raw
In response to Re: Rejecting weak passwords  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Responses Re: Rejecting weak passwords  (Kenneth Marshall <ktm@rice.edu>)
List pgsql-hackers
On Thu, Oct 1, 2009 at 15:26, Albe Laurenz <laurenz.albe@wien.gv.at> wrote:
> Andrew Dunstan wrote:
>>>> So here's the patch.
>>>> I don't think there is documentation required;
>>>> correct me if I am wrong.
>>>
>>> How will people know how to use it, or that it's even there without at
>>> least a note in the docs somewhere?
>>
>> I'd prefer to have an example as a contrib module, as well as docs.
>> Quite apart from anything else, how the heck would we test it without
>> such a thing?
>
> I was not sure because no other hooks were documented anywhere else
> than in the code.
>
> I could add a paragraph in the "auth-password" section of
> client-auth.sgml. Or is there a better place?
>
> I could easily write a simple contrib that adds a check for
> username = password if there is interest.

I think it's better to have an actually *useful* contrib module for
it, if there is one. Meaning perhaps something that links to that
cracklib thing mentioned upthread.

-- Magnus HaganderMe: http://www.hagander.net/Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Stef Walter
Date:
Subject: Re: Use "samehost" by default in pg_hba.conf?
Next
From: Simon Riggs
Date:
Subject: Re: Hot Standby on git