Feature #6649

Enable mixed_content block settings in the browser

Added by anonymousaccount 2014-02-09 11:25:41 . Updated 2018-08-19 12:06:43 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Wait
Blueprint:

Starter:
0
Affected tool:
Browser
Deliverable for:

Description

In Iceweasel, set security.mixed_content.block_active_content and security.mixed_content.block_display_content to true for higher security when using HTTPS.

Subtasks

Related issues

Related to Tails - Feature #5706: Harmonize our Tor Browser config with TBB Resolved

History

#1 Updated by sajolida 2014-02-10 08:49:47

  • Starter changed from Yes to No

Can you give us more insight on what are those options doing and why we should enable them. Maybe with external references.

Furthermore, we try to align our browser setting to the Tor Browser, so could you investigate how they are treating those options and why.

#2 Updated by BitingBird 2014-03-07 00:31:56

  • QA Check set to Info Needed

#3 Updated by intrigeri 2014-04-03 17:05:50

  • Subject changed from Enable mixed_content block settings in Iceweasel to Enable mixed_content block settings in the browser
  • Status changed from New to Confirmed
  • QA Check deleted (Info Needed)
  • Type of work changed from Code to Wait

I agree it would be good to not disable Firefox’ mixed content blocker. But in the current state of things, a quick search on Tor’s Trac explains why the MCB is disabled in the TBB: https://trac.torproject.org/projects/tor/ticket/3777

So, we have to wait for HTTPS Everywhere and Firefox to play well together again.

#4 Updated by BitingBird 2014-06-21 15:28:07

  • related to Feature #5706: Harmonize our Tor Browser config with TBB added

#5 Updated by intrigeri 2018-08-19 12:06:43

  • Status changed from Confirmed to Resolved

We now ship Tor Browser and don’t tweak these prefs.