full-disclosure - 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <40A4D680.207@nolog.org>
From: list at nolog.org (list@...og.org)
Subject: Sasser author

Hello,

Anders B Jansson wrote:
> list@...og.org wrote:
 >> you missed one point: Sasser only violates *unpatched* networks, not
 >> networks in general.
 >
> Point not missed at all.
> 
> Probing a network for vulnerabilities with the intent to use the found 
> holes for sabotage (without the owners consent) is a criminal act.

not here where I'm living. But IANAL in your country. So, it depends on 
where you are living if it's illegal or not.

> And stop this silly mumbling about Sasser being created as warning or 
> heads up.

That's your *interpretation*, not what I said. And this interpretation 
is *wrong*.

> Sasser was created to create havoc, nothing else.

ACK. But only unpatched computers were vulnerable - we had no problems 
here 'cause we've already patched our machines. So, our network was not 
violated and we had time for more important things then solving problems 
caused by a worm that could spread because of unpatched computers.

GTi