Feature #12653
Upstream changes to our Tor Browser 7.0 AppArmor profile
Start date:
2017-06-07
Due date:
% Done:
100%
Description
Subtasks
Related issues
|
Blocks Tails - |
Resolved | 2017-06-10 |
History
#1 Updated by intrigeri 2017-06-16 14:58:57
- blocks
Bug #12679: Sandbox Tor Browser's content renderer processes more strictly added
#2 Updated by intrigeri 2017-06-16 15:08:57
I need to do this (at least preparing a branch) before I can “work” on Bug #12679 for fun today, so I’ll do at least that first step. But I’m a bit confused by “Type of work = Wait”, as I see no PR on GitHub. What are we supposed to be waiting for?
#3 Updated by intrigeri 2017-06-16 15:09:13
- Assignee changed from anonym to intrigeri
#4 Updated by intrigeri 2017-06-16 15:12:01
I’ve found two candidates:
- commit:c2fc6fd77083b8c28c7aecd6b8ac7e56f1140444: on my system, TB 7.0.1 starts very well without this change. So I wonder if/why it needs to be upstream’ed, or if it’s only needed due to some custom Tails stuff (e.g. our own startup script).
- commit:f11ebadf6f5911d17a0ec0ffb7e78bd987689b60 obviously
#5 Updated by intrigeri 2017-06-16 16:07:47
- Status changed from Confirmed to In Progress
- % Done changed from 0 to 20
- Affected tool set to Browser
Sent https://github.com/micahflee/torbrowser-launcher/pull/277 along with a number of other small improvements.
#6 Updated by intrigeri 2017-06-23 07:05:19
- Status changed from In Progress to Resolved
- Assignee deleted (
intrigeri) - % Done changed from 20 to 100
Merged upstream. Next step will be to update our delta once the updated profiles make their way into Debian.
#7 Updated by intrigeri 2017-06-30 06:20:52
- Target version changed from Tails_3.1 to Tails_3.0.1