right.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;right. I need the app on my laptop and on my desktop.
2.) Upon discovering the same license on two computers at the same time, the app quits / refuses to run.
right again.
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.
well, obviously, LS isn't seeing any sort of rule error the way I have it setup [which is to deny any connection to the app except printing].
In this case I don't think it's using http or anything like that.
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.
so, I went into Activity monitor and quit the mDNS* process on both machines, but that ain't it. Very interesting and the plot thickens...
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.
Michael
_______________________________________________ Littlesnitch-talk mailing list [email protected] http://at.obdev.at/mailman/listinfo/littlesnitch-talk
