Why does Firefox 52 create inbound rules to allow TCP,UDP on all ports on private profile?
Hello, I've checked my firewall rules and found two inbound rules for firefox.exe:
Profile: Private, Protocol: TCP/UDP, Remoteport: Any
Where do these rules belong to? Which functions won't work if I disable/delete them? (I tried it, couldn't find any restrictions.) In this forum https://superuser.com/questions/882494/why-does-firefox-create-inbound-firewall-rules somebody wrote, that the rules belong to Windows Hello. But I'm using Firefox 52 and Firefox Hello was removed with Firefox 49. If I remove the rules, they are recreated by the next Firefox update.
It would be nice if you could clarify that.
Modifié le par Firefox_us3r
Toutes les réponses (6)
Push - can anyone help me with my question?
I would think not. If you are running a good Firewall you can set look there for what is really allowed to come in and on what ports as well as restrict it in the firewall rather than restrict it in Firefox. I would think that is why it is set to all as the Firewall makes the rules. Not sure if that is the reason or not.
You may find info if do your search in google with terms firefox tcp udp https://www.google.com/search?q=Firefox+tcp%2Fudp+ports&ie=utf-8&oe=utf-8&client=firefox-b
Note : it shows here you are using Firefox 52. You should be using the Extended Release Version to get Security Updates. All those extensions are vulnerable.
52.7.3 ESR. It will continue to get security updates until June 2018, and you can download and install it from this page: *https://www.mozilla.org/en-US/firefox/organizations/all/ Note : Legacy Extensions will be deleted or removed in any version update after June 2018. Firefox 52.9.0esr out on June 26 (same time as 60.1.0esr) will be the last major update for Firefox 52 ESR apart from any 52.9.x esr updates for security or allowed stability fixes.
Based on Quantum Firefox 60.2.0esr will be out Aug 21 and Firefox 52 ESR will be EOL then. So people will have to upgrade to 60.2.0esr to keep getting security updates if they have not manually upgraded to 60.x.o ESR already. Firefox 60 ESR will require Windows 7, 8, 10. You should make a backup of your Profile before going back and just because:
- https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles
- https://support.mozilla.org/en-US/kb/export-firefox-bookmarks-to-backup-or-transfer
Please let us know if this solved your issue or if need further assistance.
Pkshadow said
You may find info if do your search in google with terms firefox tcp udp https://www.google.com/search?q=Firefox+tcp%2Fudp+ports&ie=utf-8&oe=utf-8&client=firefox-b
Of couse I used Google before..
Modifié le par Firefox_us3r
I noticed your question a while ago but failed to respond back then. However, your previous response (especially to a helper who provided you with other useful info) does not invite me or others to do so after all. No wonder someone marked it as abuse - please respect the forum rules and guidelines next time.
As for your issue: like mentioned in the Superuser thread referred to, the most likely reason is to create a rule for the loopback connection, as in the past, users could run into trouble when it didn’t exist. See this bug and this bug for clarification.
If you want to be sure (and verify the first bug to be the one that implemented it), install Firefox 34 after removing the rule, then Firefox 35, or restrict the rule to 127.0.0.1 to see what happens (I’m not sure if that rule will be retained instead of overwritten though).
Also see How to stop Firefox from making automatic connections.