3 ms·
Didn't see a lot of practical advice. For example: they say there aren't really defenses against keyloggers but that is not true. One defense to protect a we
by 300bps 13y ago
Didn't see a lot of practical advice. For example: they say there aren't really defenses against keyloggers but that is not true. One defense to protect a web password is to inject characters into the key logger that are ignored by the browser. One method of doing this is to click in the password text box, type one character of your password then click on the background of the page and type a bunch of gibberish then repeat. The keylogger will be filled with random gibberish instead of your password.
- StavrosK 13y agoMost keyloggers include the window title (and the really advanced ones take screenshots as well), so this countermeasure is easily defeated.
- 300bps 13y agoI'm not sure if you understood what I was saying because the window title would remain the same (i.e. the browser). You would just be clicking inside and outside of a textbox within the same browser. As for taking a screenshot - that wouldn't help either with something meaningful like a password. Not to mention that doing screenshots totally changes the dynamic of a "key logger" and exponentially raises the amount of storage needed and makes it even more difficult to glean useful data from it. I think you're trying to stretch to make this countermeasure "easily defeated" when it really isn't.
- txutxu 13y agoWell, in my opinion, the advices are practical. Some of them require a little bit more of research by the user, but the advices are practical all of them.