I was wondering about this too. Why have dead links at all? Why doesn't the dead rule simply vanish. Though, you still would have to train the new version. Then again, why doesn't the rule simply transfer to the new version of an application in a similar way that aliases do?
-
----------------
Greg Martinez
[EMAIL PROTECTED]
iMac 17" G4, 1GHz, OS 10.3.6, 768 MB RAM.
iBook 12" G4, 800MHz, OS 10.3.6, 640 MB RAM.
-----------------
On Nov 22, 2004, at 11:08 PM, Ward Clark wrote:


I'm quite pleased with Little Snitch watching my back.

But one chronic annoyance is Little Snitch's behavior when I upgrade to a new version of an application. I typically put each application and its associated files into a folder whose name includes the version number. So each upgrade breaks the path that Little Snitch is apparently recording. The result is ...

1.  I have to retrain Little Snitch with each new release.

2. I have an increasing number of dead, red "Application does not exist at this path" rules. No only that, I can delete only one at a time, and I have to confirm each delete. OmniWeb is a worst case example. Because I install every alpha and beta release, I now have 49 obsolete rules to delete ... one at a time.

The Mac OS X Keychain and QuicKeys provide good models for graceful handling of application upgrades, either automatically handing off application assignments to a new version or providing a simple means to manually rebind to the new version.

Since this main wish may be a while in coming, I'd be happy for the time being if Little Snitch supported multiple-select and delete.

_______________________________________________ Littlesnitch-talk mailing list [EMAIL PROTECTED] http://at.obdev.at/mailman/listinfo/littlesnitch-talk

Reply via email to