Remote Assistant deletes Windows Firewall Rules Hello Ralf,
I just switched off the two options you mentioned. The rules are still getting deleted. But if this is a predicted behaviour, why only creating an inbound connection and not an outbound connection? — Ralf B
So let us make sure that we are on the same page, by expected behavior I meant creating those rules, not deleting any existing ones. As for the Inbound connection only it is pretty much simple, outbound ports are 80 and 443 which are usually open for software to use.
And why deleting manually set firewall rules in the first place? This just doesnt add up, someone just messed things up in this version. — Ralf B
This is unexpected behavior and I have already reported it to our R&D to check and correct in the next versions, I was able to reproduce it on a few test machines. However, there are things we need to consider.
Every reboot i have to manually re-set those firewall rules. If im not physically at the machine at a reboot (windows updates and such) i get locked out. That cant be an expected behaviour. — Ralf B
One of them is the usage of Windows Firewall, in my personal opinion it is garbage, it has too many flaws, it had too many exploits and basically it is not safe (over 30 CVE's publically available and who knows how many private one's) . Secondly, we have to consider the "Average Joe" that you mentioned, try explaining a novice PC user that just simply wants to connect and help his Grandma what is Firewall and how to open the ports in it.
Summarizing it all up, we surely understand what do you mean and why it is important for you and we are really grateful for pointing it out for us. I will personally make sure that we document this better and allow disabling this behavior in the next release. Thank you.