Project

General

Profile

Feature #12571

Find a nicer way to add exceptions from mandatory signing for our Tor Browser add-ons

Added by anonym 5 months ago. Updated about 1 month ago.

Status:
Confirmed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
05/19/2017
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Code
Blueprint:
Easy:
Affected tool:
Browser

Description

The current approach is 415f520fde6f84c5f32ff3769f16f42c8209137d, where we unpack and patch the relevant files in the omni.ja archives. We should upstream this to Tor Browser somehow so we don't have to carry this delta.

A discussion about this has slowly been started a while back here: https://lists.torproject.org/pipermail/tbb-dev/2017-April/000515.html


Related issues

Blocks Tails - Feature #13244: Core work 2017Q4: Foundations Team Confirmed 06/29/2017

History

#1 Updated by anonym 5 months ago

  • Target version changed from Tails_3.0 to Tails_3.1

#2 Updated by u 4 months ago

Upstream Tor bug which plans to add this to their design documentation: https://trac.torproject.org/projects/tor/ticket/21922

#3 Updated by u 4 months ago

Upstream Tor bug about unreproducible omni.ja: https://trac.torproject.org/projects/tor/ticket/21960

#4 Updated by intrigeri 4 months ago

#5 Updated by anonym 4 months ago

  • Target version changed from Tails_3.1 to Tails_3.2

#6 Updated by intrigeri about 1 month ago

u wrote:

Upstream Tor bug about unreproducible omni.ja: https://trac.torproject.org/projects/tor/ticket/21960

(Just to save anonym some time: this seems unrelated to this ticket.)

#7 Updated by intrigeri about 1 month ago

  • Target version changed from Tails_3.2 to Tails_3.3
  • Type of work changed from Communicate to Code

anonym wrote:

A discussion about this has slowly been started a while back here: https://lists.torproject.org/pipermail/tbb-dev/2017-April/000515.html

My understanding is that an agreement was reached (add a pref with the whitelist), so next step is to actually implement it. I'll let you evaluate if this is something you can do yourself, or something we should kindly ask Tor Browser developers (or other nice people we know who might want to help, Cc garrettr) to implement it themselves.

I suggest you spend a couple hours (not more!) on this evaluation during the 3.3 cycle and then adjust the timeline depending on the outcome.

#8 Updated by intrigeri 20 days ago

#9 Updated by intrigeri 20 days ago

Also available in: Atom PDF