just got that popup after launching a pdf through Chrome (using Adobe plugin and not Chrome viewer) >>> see screen shot (no app name mentioned). I found as well that there’s an adobe group that was created in the network rule list, but this group is empty in the UI, although it appears that everything has been properly registered in rules.xml
One last thing, clicking on view/override on fw popups (so on auto-decide mode) just opens the fw app list, without precisely pointing to the rule that just got created. I think it use to do that several builds ago, in 5.0 (not the last 5.0 build though).
Had these problems and some others with avast firewall (long/short filename confusion).
I’ve given up and switched to comodo (even though I still have an AIS licence). I know comodo isn’t flavour of the month just now, but the FW seems to do what I’d hoped avast would - it lets through anything it recognises as OK (which is everything except GRC leak test and one “Phone-home” pdf on my machine so far), and aks me about anything it doesn’t. It blocks anything I ask it to block.
yeah I’ve never been really happy about that (avast) firewall either. And although, for having used it a long time, I admit that Comodo firewall is better, technically more advanced etc…, I don’t think I will use it again. No major change in the interface for years now (from 3.0 up to 5.0)+ I despise this company a bit more every time I hear about them.
“Despise” is a very strong word. I tend to reserve it for racists, religious bigots, people traffickers, drug barons, investment bankers etc :).
Comodo, as I see it, are trying to make a living by doing something useful, but have lost their moral leadership a bit in terms of how to go about it. I put them in my “mildly disapprove of” category.
When I get time I’ll probably check-out another FW (but I disapprove of my bank far more than comodo, and have not yet got around to moving my account).
OK then. Just confirming that I got the same pop-up problem, so it is not unique to your system, and that I got it in 5.0, so it is not a new 5.1 issue.
