Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • I don't meant, that the "mapping tool" don't know the password.
    – Artery
    Commented Nov 14, 2016 at 19:49
  • 1
    By definition, keylogger will record all K&M inputs. So the only way to get around that is to authenticate not using K&M and/or reusable credentials. Things like tokens with rolling code will offer reasonable protection. Now in practical terms, you are likely safe using throw-away password then changing it from a trusted system once you finished with untrusted device. You are counting on the fact that 'nobody home' at the other end of keylogger.
    – Kirill Sinitski
    Commented Nov 14, 2016 at 19:49
  • @KirillSinitski Are there any (common) ways to do so?
    – Artery
    Commented Nov 14, 2016 at 19:52
  • It's better to not use a system you think will have a keylogger running. Any schema you can think about is a schema the keylogger maker could possibly have thought before you.
    – ThoriumBR
    Commented Nov 14, 2016 at 19:54
  • In the novel Cryptonomicon, the protagonist extracted data from PC that was suspected of being bugged by flashing Morse code on the Caps Lock LED. You could do the opposite, use the shift key as a Morse sender, as key loggers really don't record timing, only codes
    – infixed
    Commented Nov 14, 2016 at 19:55