| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | marcin mank <marcin(dot)mank(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Marko Kreen <markokr(at)gmail(dot)com>, Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, Andrew Dunstan <andrew(at)dunslane(dot)net>, mlortiz(at)uci(dot)cu, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Rejecting weak passwords |
| Date: | 2009-09-28 22:52:56 |
| Message-ID: | 4AC13E48.1070009@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> It takes about 32 hours to brute force all passwords from [a-zA-Z0-9]
> of up to 8 chars in length.
That would be a reason to limit the number of failed connection attempts
from a single source, then, rather than a reason to change the hash
function.
Hmmm, that would be a useful, easy (I think) security feature: add a GUC
for failed_logins_allowed.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-09-28 22:57:17 | Re: TODO item: Allow more complex user/database default GUC settings |
| Previous Message | decibel | 2009-09-28 22:52:18 | Re: TODO item: Allow more complex user/database default GUC settings |