On May 1, 2005, at 17:12, Michael Spencer wrote:
And, you guessed it: the app has discovered itself. I have no clue how this is happening. Any ideas?
I'm going to assume that by 'discovered itself' you mean:
1.) The app in question found a copy of itself on your second computer;
2.) The copy is licensed with the same serial number;
2.) Upon discovering the same license on two computers at the same time, the app quits / refuses to run.
The apps I know of that do this -- not so much 'calling home' as 'calling around the neighborhood' are the Microsoft Office applications, Final Cut Pro and PopCharX. It's simple enough to stop the Office Suite apps from checking the local net for a matching license -- just turning on the OS X firewall disables the port they use.
As for the other two, it's a different story. They use Rendezvous (renamed 'Bonjour' in Tiger) to do their license checking. This way, LS sees no rule violation because the port is bound by Rendezvous rather than the application itself.
Other ways applications can get out past LS are to highjack your browser and connect to a site with a little info-divulging header script attached or to have a script written in a language -- java, say, or python -- to which you've given 'connect any server / protocol' permissions. But since we're talking about your local network, I'd be pretty it's using Rendezvous.
Rendezvous / Bonjour's *other* name -- as far as the system itself is concerned -- is mDNSResponder -- there's a rule for it in LS. Edit it at your pleasure, but remember you'll lose the Rendezvous features -- which may or may not be important to you.
_______________________________________________ Littlesnitch-talk mailing list [email protected] http://at.obdev.at/mailman/listinfo/littlesnitch-talk
