#23258: HTTPS Everywhere is not working when noscript is enabled globally --------------------------------------+-------------------------- Reporter: Dbryrtfbcbhgf | Owner: tbb-team Type: defect | Status: assigned Priority: High | Milestone: Component: Applications/Tor Browser | Version: Severity: Major | Resolution: Keywords: TorBrowserTeam201708 | Actual Points: Parent ID: | Points: Reviewer: | Sponsor: --------------------------------------+--------------------------
Comment (by yawning): Replying to [comment:16 gk]: > Replying to [comment:15 gk]: > > I guess what we can and maybe even should do is whitelist `moz- extension:` (see #21270). That solves the problem for me. However, it causes a startup delay of several seconds on my Linux debug build. So, hrm. > > So, the startup delay is not related to the whitelisting but to the new HTTPS-E itself. :/ That's unfortunate especially for people that use amnesiac setups like Tails or the experimental sandbox option. What is HTTPSE doing during the startup delay? Is it something that can be accelerated by pregenerating things during the build process? As far as I am aware, the plan is to disable automated updates (that aren't done via the Tor Browser update process, as in, via a MAR), so the delay could be eliminated... -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/23258#comment:19> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs