Bug #9219

Obsolete tweak to Pidgin's AppArmor profile?

Added by intrigeri 2015-04-09 13:05:50 . Updated 2015-04-27 03:53:27 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_1.4
Start date:
2015-04-09
Due date:
% Done:

100%

Feature Branch:
Type of work:
Test
Blueprint:

Starter:
Affected tool:
Browser
Deliverable for:

Description

config/chroot_local-patches/apparmor-adjust-pidgin-profile.diff, introduced by commit:ee4eefc, allows running /usr/local/bin/tor-browser unconfined. Is this still needed? We should at least check that this doesn’t result in running Tor Browser unconfined (shouldn’t be the case since our Tor Browser profile applies directly to /usr/local/lib/tor-browser/firefox, but still).

Subtasks

History

#1 Updated by intrigeri 2015-04-27 03:53:27

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100
  • Parent task deleted (Feature #8007)
  • Affected tool set to Browser

Ux is exactly what we need: we have no profile for the /usr/local/bin/tor-browser script, so we can’t use Px. And when that script runs firefox, the latter is automatically attached to its own profile. I’ve verified that it’s the case both when Tor Browser is already running, and when its startup is triggerred by clicking a link in Pidgin.