1 Feb 02:01
Re: super-restrictive IPtables
jen montserrat <jen.montserrat <at> gmail.com>
2012-02-01 01:01:49 GMT
2012-02-01 01:01:49 GMT
80% of those Windoze systems not 0wned, how many actually are but the users are totally unaware that they are 0wned? You could run Tinyproxy with Dansguardian and then use the filters in Dansguardian to restrict where the XP host can go via the web, if at all? Then use IPTABLES to further restrict. This is also a configuration from squid to allow windows update that should be placed at the top of the acl. acl windowsupdate<http://linuxpoison.blogspot.com/2008/04/howto-allow-windows-updates-through.html#>dstdomain windowsupdate.microsoft.com acl windowsupdate dstdomain .update.microsoft<http://linuxpoison.blogspot.com/2008/04/howto-allow-windows-updates-through.html#> .com acl windowsupdate dstdomain download.windowsupdate.com acl windowsupdate dstdomain redir.metaservices.microsoft.com acl windowsupdate dstdomain images.metaservices.microsoft.com acl windowsupdate dstdomain c.microsoft.com acl windowsupdate dstdomain www.download.windowsupdate.com acl windowsupdate dstdomain wustat.windows<http://linuxpoison.blogspot.com/2008/04/howto-allow-windows-updates-through.html#> .com acl windowsupdate dstdomain crl.microsoft.com acl CONNECT method CONNECT acl wuCONNECT dstdomain www.update.microsoft.com http_access allow CONNECT wuCONNECT localnet http_access allow windowsupdate localnet(Continue reading)
RSS Feed