Horton

Re: Rejecting weak passwords

Tom Lane <tgl@sss.pgh.pa.us>

View thread View on postgr.es
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Albe Laurenz" <laurenz.albe@wien.gv.at>
Cc: "Bruce Momjian *EXTERN*" <bruce@momjian.us>, "Robert Haas" <robertmhaas@gmail.com>, "Mark Mielke" <mark@mark.mielke.cc>, "Dave Page" <dpage@pgadmin.org>, "Kevin Grittner" <Kevin.Grittner@wicourts.gov>, "Andrew Dunstan" <andrew@dunslane.net>, "Marko Kreen" <markokr@gmail.com>, "Magnus Hagander" <magnus@hagander.net>, "Greg Stark" <gsstark@mit.edu>, "pgsql-hackers" <pgsql-hackers@postgresql.org>, "mlortiz" <mlortiz@uci.cu>
Date: 2009-10-19T14:30:05Z
Lists: pgsql-hackers 
"Albe Laurenz" <laurenz.albe@wien.gv.at> writes:
> Bruce Momjian wrote:
>> Password checks might include password complexity or non-reuse of
>> passwords. This facility will require the client to send the password to
>> the server in plain-text, so SSL and 'password' authentication is
>> necessary to use this features.

> So in my opinion that should be:
> This facility will require to send new and changed password to
> the server in plain-text, so it will require SSL, and the use
> of encrypted passwords in CREATE/ALTER ROLE will have to be
> disabled.

Actually, not one word of *either* version should be in TODO.  All of
that is speculation about policies that a particular add-on module
might or might not choose to enforce.

			regards, tom lane