On Wed, Jun 27, 2007 at 10:37:59AM -0700, 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?
There are rules; some come with the firewall, some I created, and some were set up the first time a particular connection was initiated. For example: o IE and Firefox are allowed to connect to anywhere on port 80. o SecureCRT is allowed to connect anywhere over SSH sockets. o Visual Studio is allowed to connect to the MS Update site. > 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 > > -- > PDML Pentax-Discuss Mail List > [email protected] > http://pdml.net/mailman/listinfo/pdml_pdml.net -- PDML Pentax-Discuss Mail List [email protected] http://pdml.net/mailman/listinfo/pdml_pdml.net
