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

Message-ID: <20040506102748.GB8342@ics.muni.cz>
From: krajicek at ics.muni.cz (Ondrej Krajicek)
Subject: Learn from history?

> 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?

Anyone? I'am really curious if someone dares to use this for 
production-level security.

With no logs, you must rely on pen-testing
to make sure it works. Beside the burden of hacking of your
own _production_ box, as always with group policy,
you never know when it stops to work.

Just my $0.02...

Ondra Krajicek

+>>>-----------------------------------------------------------------+
|Ondrej Krajicek                                                 (-KO|
|Institute of Computer Science, Masaryk University Brno, CR          |
|http://isildur.ics.muni.cz/~ondra               krajicek@....muni.cz|
+--------------------------------------------------------------------+