full-disclosure - Re: Most common keystroke loggers?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <439030F5.31961.2C5AC6B8@gmail.com>
Date: Thu Dec  1 22:33:30 2005
From: nick at virus-l.demon.co.uk (Nick FitzGerald)
Subject: Re: Most common keystroke loggers?

Dave Korn wrote:

>   How about one-time passwords?  Just go ahead and *let* them keylog it all 
> they like; by the time they've snarfed a pw, it's no use any more.  (See 
> S/Key for more details.)

Ignoring the silliness of pre-printed lists of of OTP (such as some 
European banking systems' TANs) and the ease of extracting a few from 
gullible users, even dynamically generated OTPs are still vulnerable to 
man-in-the-middling _if_ the bad guy has code running on the device by 
which the user interacts with whatever service the OP is hoping to 
"protect".  I know the OP said "keylogger compromised", but if the 
machine _is_ compromised (and you can't tell from your remote web 
server) as the folk running the server you have no control over how it 
was compromised, so that is a chronically arbitrary condition (which 
suggests to me that the OP doesn't understand his actual problem set).

Regards,

Nick FitzGerald