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]
From: geoincidents at getinfo.org (Geoincidents)
Subject: Re: Gates: 'You don't need perfect code' for good security

> First, firewalling and patching can not in fact shield networks from
> all of the impact of worms and viruses. Ask any experienced network
> admin. There will always be users who bring into a firewalled network
> a laptop that was, for example, infected at home.

Part of the problem here is network design. For example, if when laptops are
brought in they were only allowed to connect to a wireless network and that
wireless network was on the far side of the firewall (perhaps slightly more
access than from the internet but still majorly firewalled) and treated as
untrusted systems which they in fact are, then it would not be such an
issue.

There is no rule that says you can't have internal firewalls to separate
untrusted from trusted systems. But you have to design your network around
this idea for it to work.

Geo.


Powered by blists - more mailing lists