full-disclosure - Learn from history?

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-next>] [day] [month] [year] [list]

Message-ID: <04F92BA33955D51195B700508B4AB6E917700859@dslak12.dnznet.co.nz>
From: StuartF at datacom.co.nz (Stuart Fox (DSL AK))
Subject: Learn from history?

> 
> > 3. If it is a port-related threat, find out if such ports 
> are in use, 
> > and if not, make sure they are closed. (Of course there would
> 
> Once the virus is on the LAN it can do whatever it wants.
> 
Not quite.  Anyone here using IPSEC filter group policies to block the ports
that Sasser uses to propagate?  Obviously you can't block 445 without
causing significant issues, but you can block the ports Sasser uses to
transfer itself (5554 & 9996).

Anyone here using IPSEC Filter Group Policies at all?