Re: firewall securing outgoing traffic?
From: Bruno Wolff III (bruno@cerberus.csd.uwm.edu)Date: 01/29/02
- Next message: Bo Jacobsen: "How to "save" the current iptables setup"
- Previous message: Juha Laiho: "Re: Tripwire problem (st_ctime)"
- In reply to: Dimitri Maziuk: "Re: firewall securing outgoing traffic?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: Bruno Wolff III <bruno@cerberus.csd.uwm.edu> Date: 29 Jan 2002 20:42:58 GMT
In article <slrna5dvfu.7va.dima@odyssey.bmrb.wisc.edu>, Dimitri Maziuk wrote:
>
> This doesn't really work: presumably the code that calls home is
> hidden inside some application that _you've_installed_because_you
> _wanted_to_use_it. If it needs network access for legitimate
> reasons, you can't block it (or you can't use it).
As you mention below, port blocking won't work; however, blocking by
IP address can work in many cases.
My perception is that game companies are getting more aggressive in trying
to get marketting information about people who use their games and I don't
trust them to not try to have their games call home. However, I expect
that playing some multiplayer games using peer to peer connections under
linux is something I will want to do within the next year.
I also might get stuck running some proprietary clients at work in the
near future on my linux box.
> Similarly, it can use a "legitimate" port when it calls home (e.g.
> it calls a CGI script), so trying to block on per-port basis won't
> work either.
- Next message: Bo Jacobsen: "How to "save" the current iptables setup"
- Previous message: Juha Laiho: "Re: Tripwire problem (st_ctime)"
- In reply to: Dimitri Maziuk: "Re: firewall securing outgoing traffic?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
