Godfrey DiGiorgi wrote: > On Jun 27, 2007, at 9:16 AM, John Francis wrote: > >>> I'm not sure why this is a concern. I don't care if an application >>> does a check for registration/license. My networking firewall is >>> designed to detect and notify me of intrusion attempts from the >>> outside, not from connections originating from inside it's >>> boundaries. >> So, if you ever get hit by a Trojan Horse, you'll never know about it. >> >> My firewall software (just like many other similar products) will tell >> me about unrecognised connections initiated from inside the firewall. > > How does your software discriminate between an authorized connection > to a new destination initiated from inside the firewall and an > "unrecognised" connection? What are the criteria it uses as a > distinction? > > I have all kinds of things that look outbound for stuff independent > of my user process without my having to interact with them. I don't > know how I'd tell a firewall what was recognized and what wasn't... > > G >
Generally this is tracked on a per-program basis. The first time a program initiates an outbound connection you are asked to authorize it, afterwards the Firewall software remembers what has been authorized. Some firewall packages offer a third 'one time' authorization option as well. Windows Vista's firewall includes this functionality, and it's rather transparent after the first couple of days (as your network apps get their authorizations). -Adam -- PDML Pentax-Discuss Mail List [email protected] http://pdml.net/mailman/listinfo/pdml_pdml.net
