I know the LnS team has been busy dealing with the leaktests and is probably working on WallBreaker now. However, at one point, it should make the filtering rules more user-friendly. One way to do that is to use a WIZARD that holds the hand of the user to guide him in making rules, explaining what the parameters are. Once this is done, full use of this software's potential would not be limited to a few. The immediate practical application is not only better protection for all users, but more $$$ or Euros ! And for a commercial venture this is nothing to sneeze at. In fact, great ventures have died because of neglect of those non-knowledgeable in a particular jargon (even if these happen to be PhDs in chemistry or math who are fluent in their own specialist jargons -- so he who does not know a particular specialty is not necessarily stupid). Regarding application filtering, ZAP has this great feature where the great masses are easily empowered to set Internet access for an app BUT deny it server privilege by just 2 clicks. I guess this can be made in LnS through a rule too. But why not make it simpler and speedier, right in the application filtering window, with just a click? Finally, concerning "fingerprinting". Since LnS appears to be more successful than ZAP in stopping leaks, I would assume that it fingerprints programs too, like ZAP. However, in the trial period I did not seem to remember LnS stopping me because a file had a different signature. I will look harder and systematically upgrade something to see if LnS will let it go through. I hope you find these suggestions constructive.