Re: Firewall against Windows XP?

From: Mark Atherton (n_z_w_nguregba_at_lnubb.pb.hx)
Date: 07/01/03


Date: Tue, 01 Jul 2003 22:37:26 +0100

Carlos Moreno wrote:
>
> Hi there,
>
> I have a home LAN protected by a Linux box that acts as a
> Gateway/router/firewall (currently setup with iptables,
> "stealth" mode).
>
> I currently use Linux and Windows 2000 on my internal
> machines, but I may be "forced" to switch to Windows XP
> (professional, I guess) in the near future (you know,
> the usual story )8-[ )
>
> Anyway, I'm always be terrified of using Windows XP,
> which I regard as the worst threat to the privacy and
> security of my machines, my privacy, information, etc.
>
> I was wondering if you guys have experience with this
> setup (I'm talking about a Linux-based gateway/firewall
> to protect a network that has computers with WinXP among
> others). Any specific ports that I need to block to
> prevent Windows XP from doing its funny thing??
>
> I'm even terrified to simply put a strong firewall for
> the incoming stuff -- it terrifies me that Windows XP
> might willingly share my information without my knowing
> it. I wonder if there is a list of ports that I should
> block on both directions? (something that would not
> affect regular usage of the web, e-mail, ftp downloads,
> SSH, etc.). I might even be willing to unconditionally
> block traffic to or from www.microsoft.com, www.hotmail.com,
> MSN, etc. (if that does makes any sense -- you know, being
> paranoid as I am, and so profoundly uninterested in stuff
> from Microsoft, I think it could make sense).
>
> (yes, I know, I know I seem to be sending mixed signals...
> So uninterested in Microsoft stuff, but currently using
> Win2K and thinking of switching to WinXP... *sigh*, this
> world is so depressing, I know :-))
>
> Thanks for any advice or pointers!
>
> Carlos
> --
>

I block everything in both directions and run daemons on the gateway
machine for any services I want workstations to have access to.

That means squid acting as http/https/ftp proxy and also running dns,
ntp and nntp servers. I also run a mail server (postfix, imap,
fetchmail) so there is no need for any direct connections to pass
through the firewall either in or out.

Off course spyware can still communicate with home using http, but at
least there will be a trace in the squid logs.

Now, one thing I haven't managed to do is configure squid to refuse
access on IP address if a reverse dns lookup fails. My logic is that at
least if the IP address is linked to a domain name I have a chance of
finding out who is receiving outgoing connections from spyware within my
LAN. Is this worthwhile? If so, can it be done?

Mark Atherton



Relevant Pages

  • Re: Update while you can...
    ... integrated into Linux, MS "might" have some serious competition. ... There are several directions things may go. ... I have yet to understand that are related to their license stuff. ... but I don't see how MS will be able to fully enforce it under XP. ...
    (alt.computer.security)
  • Re: MS02-052 coporate install file??(q329077)
    ... I happen to be looking at Linux as well, ... >Everything points back to the winupdate site. ... Winupdate site's>directions ... >how to show direct links to update files is outdated and no longer ...
    (Security-Basics)
  • Re: bridging plus caching using squid
    ... What you need is to implement NAT in your linux box, and from there, ... transparently redirect the web traffic to squid and the rest to the web. ... bridging plus caching using squid ...
    (Security-Basics)
  • Re: Runing 2 squids
    ... if squid does get confused (two ... The exact same thing happens with outbound packets. ... > linux is smart enough to realize that the addressed ip is the same ip as ... If you want to learn a little about "routing with loops", ...
    (Debian-User)
  • Re: linux for dummies book
    ... > have been published over the years with various versions of Red Hat Linux, ... > download the ISO's that match the version included with the book. ... > download the non-SRPMS ISO's and burn them following the directions found ... > If you don't have a 'burner' then you can still install by using the ISO's ...
    (linux.redhat.install)