Re: Detecting/Preventing Dictionary Attacks
From: Joe Fallon (jfallon1_at_nospamtwcny.rr.com)
Date: 12/03/04
- Next message: Blmn: "Gmail-like or Orkut-like interface"
- Previous message: Ron Weldy: "Re: Trouble moving servers with asp.net"
- In reply to: Jim Slade: "Detecting/Preventing Dictionary Attacks"
- Next in thread: WJ: "Re: Detecting/Preventing Dictionary Attacks"
- Reply: WJ: "Re: Detecting/Preventing Dictionary Attacks"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 2 Dec 2004 20:11:22 -0500
Locked accounts are typically a "bad" idea.
I implemented a CAPTCHA control instead.
Keep track of failed logins and when it exceeds your number (say 2 or 3)
then you display a CAPTCHA control with a random number or phrase on it that
a human can read but a program can't.
I also put the thread to sleep as a multiple of the number of failed log-ins
so if they keep getting it wrong it takes longer and longer to log in.
I think you can find sample CAPTCHA code using Google.
-- Joe Fallon "Jim Slade" <Jimbo@SladeIntl.com> wrote in message news:%23Z1c7vM2EHA.3132@TK2MSFTNGP14.phx.gbl... > I've been doing some research on security and it seems like > hashing/salting > passwords is a good idea - but still not really all that secure against > dictionary attacks (the salt just makes the hacker run their dictionary > against every single account - not much of a challenge for a competent > hacker) > > Just wondering what value would be added by adding some column to the > database to record failed login attempts. The idea would be that the > column > holds an integer value that gets incremented on every failed login > attempt. > Then when it reaches some arbitrary value (say 10 failed attempts), that > particular account gets "locked" out (i.e., the validation logic would not > even try to validate the user after 10 failed attempts) and the user is > informed that they need to jump through some hoops in order to unlock the > account (call tech support or whatever). Also, this counter for failed > login > attempts would get reset to zero on every successful login attempt. > > Is doing something like this a good idea? Bad idea? > >
- Next message: Blmn: "Gmail-like or Orkut-like interface"
- Previous message: Ron Weldy: "Re: Trouble moving servers with asp.net"
- In reply to: Jim Slade: "Detecting/Preventing Dictionary Attacks"
- Next in thread: WJ: "Re: Detecting/Preventing Dictionary Attacks"
- Reply: WJ: "Re: Detecting/Preventing Dictionary Attacks"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|