Forums
New posts
Search forums
News
Security News
Technology News
Giveaways
Giveaways, Promotions and Contests
Discounts & Deals
Reviews
Users Reviews
Video Reviews
Support
Windows Malware Removal Help & Support
Inactive Support Threads
Mac Malware Removal Help & Support
Mobile Malware Removal Help & Support
Blog
Log in
Register
What's new
Search
Search titles only
By:
Search titles only
By:
Reply to thread
Menu
Install the app
Install
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Forums
Software
Browsers
Firefox
LibreWolf Browser - A fork of Firefox, focused on privacy, security and freedom
Message
<blockquote data-quote="wat0114" data-source="post: 1033977" data-attributes="member: 91306"><p>Tried this browser in Linux, I don't like it. Why on earth would a browser depend on remote TCP Port 80, especially when Enable HTTPS-Only Mode is selected? Firefox doesn't require that port. The problem is reproducible and the firewall logs prove it with blocked connection attempts to 80 if the Allow rule for the port is not present. What's really odd are the "Secure Connection Failed" results, but the logs match exactly the time when these happen, and it's always remote port 80 being blocked, not 443, the latter of which i of course have a rule for.</p><p></p><p>[ATTACH]274212[/ATTACH]</p><p></p><p>If I create the rule for Port 80, Librewolf will connect no issues, even for secure (HTTPS) connetcions.</p></blockquote><p></p>
[QUOTE="wat0114, post: 1033977, member: 91306"] Tried this browser in Linux, I don't like it. Why on earth would a browser depend on remote TCP Port 80, especially when Enable HTTPS-Only Mode is selected? Firefox doesn't require that port. The problem is reproducible and the firewall logs prove it with blocked connection attempts to 80 if the Allow rule for the port is not present. What's really odd are the "Secure Connection Failed" results, but the logs match exactly the time when these happen, and it's always remote port 80 being blocked, not 443, the latter of which i of course have a rule for. [ATTACH alt="Librewolf blocked pages.png"]274212[/ATTACH] If I create the rule for Port 80, Librewolf will connect no issues, even for secure (HTTPS) connetcions. [/QUOTE]
Insert quotes…
Verification
Post reply
Top
