Skip to main content

Timeline for How easily are keyloggers foiled?

Current License: CC BY-SA 3.0

12 events
when toggle format what by license comment
Mar 17, 2017 at 13:14 history edited CommunityBot
replaced http://security.stackexchange.com/ with https://security.stackexchange.com/
Jul 2, 2016 at 23:01 comment added O'Niel @DanBeale And how'd you implement password-hashing than? "abcdefghijklm" doesn't give the same hash as "bch". You could generate the hashes of "bch", "abc",... when the password is registered, but that'd be highly insecure because if you than in your database have a column named firstSecondandEight_character_of_password, a hacker only has to bruteforce 3 characters to know your first, second, and eight character of actual password. If your pass would than be only 8 characters long, he just has 5 to left.
Jul 2, 2016 at 5:00 history edited techraf CC BY-SA 3.0
added 2 characters in body
Oct 16, 2011 at 14:36 vote accept Pacerier
Oct 4, 2011 at 8:23 answer added this.josh timeline score: 15
Oct 3, 2011 at 22:05 answer added Michał Šrajer timeline score: 5
Oct 2, 2011 at 22:05 comment added David Schwartz I think Dan means something like this: Say your password is 'moose'. The site could say "enter the third character of your password, then a 'z', then the fifth character, then a 'q' ..." the user would enter "ozeq..." and a keylogger would get mostly gibberish. (If you want to get crazy, it could even say "then enter the letter before the second character or your password".)
Oct 2, 2011 at 13:23 comment added Pacerier @DanBeale I'm not understanding you Dan
Oct 2, 2011 at 10:40 comment added DanBeale The site asking for the password could only ask for certain character (what is the second, third, and eighth character?).
Oct 2, 2011 at 7:02 history tweeted twitter.com/#!/StackSecurity/status/120393226808066048
Oct 2, 2011 at 2:24 answer added Bernie White timeline score: 32
Oct 2, 2011 at 1:06 history asked Pacerier CC BY-SA 3.0