I too have noticed the same thing. I am just a novice, but would seem you could block a application without blocking the browser without doing a work around. As to who is calling home i would hope in the near future the connections log would show as a example, “http”//comodo.com" instead of “22.214.171.124”. Having said this I am a supporter of Comodo FW Pro. Darth
If it is a bug or feature depends on what the dev intended it to do.
It’s a save way to handle things. Component a uses (or wants to) component b. Component b has access to the internet. The really save way is to block component b completly because you cannot be sure what new way there is to gain access.
Now its the users turn to check if that component a should have access to component b or not.
If not, why does it try anyways?
And why do you have to reboot the system? Well, usually it should be enough to restart the application but if some parts of it stay active in the background it doesnt count as restart —> PC reboot.
Don’t get me wrong, I ain’t the type of guy who defends something no matter what. Every software has bugs, if it doesn’t it only means nobody found one yet. ^.^
But this “feature” is one. Of course, you could suggest to implement a switch to the behaviour you mentioned.