This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/anti-abuse-wg@ripe.net/
[anti-abuse-wg] [cooperation-wg] WannaCry Ransomware
- Previous message (by thread): [anti-abuse-wg] [cooperation-wg] WannaCry Ransomware
- Next message (by thread): [anti-abuse-wg] [cooperation-wg] WannaCry Ransomware
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Suresh Ramasubramanian
ops.lists at gmail.com
Mon May 15 15:12:56 CEST 2017
On 15/05/17, 6:38 PM, "anti-abuse-wg on behalf of peter h" <anti-abuse-wg-bounces at ripe.net on behalf of peter at hk.ipsec.se> wrote: > The main route of attack is by SPAM. > Why is noone doing something effective against SPAM ? I thought the fine people here weren’t the internet police? :) Or so quite a few folks get assured when anything effective against spam gets discussed. More seriously, spam isn’t more than an initial vector. It then appears to spread via open windows shares, to other unpatched machines. There are a wide variety of takedown and mitigation actions possible here – sinkholing c2 domains, cleaning up infected machines on people’s networks, locking down firewall ACLs to prevent this from spreading unchecked etc. --srs
- Previous message (by thread): [anti-abuse-wg] [cooperation-wg] WannaCry Ransomware
- Next message (by thread): [anti-abuse-wg] [cooperation-wg] WannaCry Ransomware
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]