The only program the Detect button found on my computer was Malwarebytes, and everytime I added it to the whitelist, it was found again when I ran Detect again, so my experience is simply that Tinywall isn't familiar with any programs anyone has ever used other than Malwarebytes.Ĭlick to expand. I have unblocked blocked programs only to find them blocked again, so Avira has yet to update av definitions even though I completely whitelisted all Avira possible processes. My only real choices are to either keep Tinywall on learning mode forever, or keep trying to find the right exes/processes to whitelist for all these unknown, obscure little programs like Avira, Firefox, Chrome, Sandboxie, Cyberreason, Ccleaner ( don't even get me started on that virus ridden crapfest btw) etc., ad nauseum. It would be interesting to see if others observe lack of connectivity after install.It was such a nice easy program to install and configure on the fly, but it doesn't keep track of anything without learning mode constantly on, which basically defeats the purpose of a firewall, especially as there are some programs I have that phone home when started and I would like to be able to control that. So there is something different, no doubt about it, but i have no idea if it s related to the rule-set imported from the official one or something else, there is something changed in the new version. Hitman Pro was also NOT detected as trying to Connect in Connections page, until I've added an Allow remote UDP port 53 for svchost.exe. With the TEST 3.0.4, in my usage scenario, i have had to make a rule for Firefox to Allow connection to remote port UDP 53, to be able to connect, even though the DNS service was checked as allowed in there. No other software without an Allow UDP Remote port 53 can connect at this time.So the OS is contained well and settings work as they should. If i add an Allow UDP remote port 53 for Firefox, i can navigate the internet, even if the DNS Service is unchecked/blocked in the firewall, via that option. If the the DNS service rule is unchecked, in the router (NAT or traffic) log there is no DNS call made, during, at start or when restarting the PC. With the official 3.0.4, in my usage scenario i have the following behavior : New W10 version is not yet offered though for my system I only have checked the ICMP Filtered, the DNS and the DHCP services on that page.I enable the updates in there only if i manually check for updates. With the official 3.0.4 i see no issues in relation to the DNS calls, as the software and it s settings are designed to manage them. LE3:I have uninstalled it and reinstalled the official version after a few hours. LE2:Forgot to add something.In the Recommended Section within the general settings, the DNS and the DHCP services are checked of course.So they were allowed. LE:Other:The version name in this test build is still 3.0.4 I ll see how it goes for a few days more. The first impression is that this version is better. I ve also observed something strange though, comparing with the previous experience, the HitmanPro.exe was not showing up in the Connection window at all, so to make some rules from there.Giving Svchost.exe a UDP 53 Out rule fixed the issue, (only) then HitmanPro.exe showed up in the Connection window and a rule was added for HTTP manually, from there. To test the fix for the window i have deleted the HitmanPro existing rule and tried to do a scan.As no DNS was allowed for the svchost.exe, no connection was made from the HitmanPro.exe either. Keep in mind the DNS Client service is Always ON in W10 and that before installing the test version this Allow UDP remote 53 rule was not needed (Windows Updates beeing off in the panel). Now the firewall catches the svchost better it seems, judging by behaviour of the DNS service.I have no ideea if it s because of the new version or due to something else, as Kaspersky Free was already installed now.The original version 3.0.4 was installed when Windows Defender was On, no KAV installed at that time.Īfter loading the saved configuration, to be able to make a Firefox connection, a rule for UDP Out port 53 had to be added in the Firefox Custom Rule. Installation steps were the following: saved the configuration of the official 3.0.4, uninstalled it, restarted the PC, then installed the new 3.0.4 test version and finally loaded the previously saved configuration.īehaviour seems to be a little different though, filtering wise as well (maybe installation went different for some reason).I have observed a few things. Keep in mind I am still on version 1909 of W10Pro, so i do not know (yet) how it behaves on latest W10 version. So now, when you unblock an app, from the Connections window, a new window, to customize the APP connections, shows up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |