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: <04F92BA33955D51195B700508B4AB6E91770083D@dslak12.dnznet.co.nz>
From: StuartF at datacom.co.nz (Stuart Fox (DSL AK))
Subject: Learn from history?

> 
> > > 2. If a patch cannot be installed, find workarounds
> >
> > That does not work with the workarounds customer need to facilitate 
> > life (security <> easy of use, remember)
> 
> In the particular case of Sasser, workarounds indicated in KB 
> 835732 and/or making sure TCP 445 is closed to the outside 
> world was enough and not difficult to achieve.
> 
Not it wasn't enough.  It would be until someone dialled to the Internet, or
even to some other third party network that had the virus.  The only thing
that was enough was to patch.  The only people who have the luxury of not
patching are those who have no connectivity from their LAN to any other
network.