full-disclosure - Fw: Sasser author

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 for Android: free password hash cracker in your pocket

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

Message-ID: <40A62AE6.11558.1F3E0E51@localhost>
From: nick at virus-l.demon.co.uk (Nick FitzGerald)
Subject: Fw: Sasser author

William Warren to Paolo Mattiangeli's grizzle about being Sasser'ed at 
home:

> any firewall even the one inside xp would have stopped sasser and you 
> would have been able to patch at your leisure.

And, depending on your network architecture, it can be even easier than 
that.  Why would any vaguely competent system admin even have the 
services that Sasser depends on bound to their Inernet-facing network 
interface in the first place??

Yeah -- I know, ethernet to DSL/cable/satellite/etc which doubles as 
the "house LAN" interface.  So far all the SOHO users I've helped clean 
up Sasser have been on dial-up so why does MS still insist on binding 
MS client (and F&P ??) to dial-up interfaces by default?

-- 
Nick FitzGerald
Computer Virus Consulting Ltd.
Ph/FAX: +64 3 3529854