| From: | "Jean-Yves F(dot) Barbier" <12ukwn(at)gmail(dot)com> |
|---|---|
| To: | Mike Thomsen <mikerthomsen(at)gmail(dot)com> |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Locking out a user after several failed login attempts |
| Date: | 2011-06-29 16:00:36 |
| Message-ID: | 20110629180036.6635c4de@anubis.defcon1 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
On Wed, 29 Jun 2011 11:43:00 -0400, Mike Thomsen <mikerthomsen(at)gmail(dot)com>
wrote:
> Yes, we're logging all connections to the database.
I'm interested into that (you can it send to me as a PM.)
So, you just have to add a counter to your login table:
+------------------------------------+
| |
login attempt-----good----reset CTR to 1 |
| |
bad |
| |
CTR += 1 |
| |
CTR > 3?-------no-----------------------+
|
yes
|
revoke connect from bastarduser (until manually re-granted by dbA)
trigger alarm in security dpt
send 450kV into user's keyboard
--
Q: What do you call a half-dozen Indians with Asian flu?
A: Six sick Sikhs (sic).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Weitzenfeld | 2011-06-30 02:07:35 | Connecting to PostgreSQL server |
| Previous Message | Merlin Moncure | 2011-06-29 15:48:28 | Re: pg_advisory_locks in a multithreaded application context |