Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 972
    • Issues 972
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #10925
Closed
Open
Issue created Jan 13, 2016 by intrigeri@intrigeriMaintainer

I2P is not confined by AppArmor anymore

Originally created by @intrigeri on #10925 (Redmine)

On Tails/Jessie, I2P is managed by a native systemd unit, that tries to confine I2P with AppArmor using AppArmorProfile=system_i2p. This is correct, except that AppArmor support was enabled in Debian’s systemd 218-4, so on Jessie this is a no-op, and as a result I2P is not confined at all.

For Tor, we’re affected as well and we do config/chroot_local-patches/apparmor-adjust-tor-profile.diff. Given the use of /usr/sbin/wrapper I don’t think this is applicable as-is for I2P, so I think that on Jessie, we need ExecStart to run a shell wrapper that uses aa-exec.

Feature Branch: bugfix/10925-I2P-AppArmor

Parent Task: #7724 (closed)

Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking