Tor cannot start `obfs4proxy` ('Operation not permitted')
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tor (Debian) |
Fix Released
|
Unknown
|
|||
tor (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
After upgrading to 16.04 tor is not start as service anymore, I have checked this `/var/log/tor/log` and it says:
Apr 10 10:11:34.000 [notice] Signaled readiness to systemd
Apr 10 10:11:35.000 [warn] Could not launch managed proxy executable at '/usr/bin/
If I stop tor service and I start tor with my user everything works fine so it looks something related to apparmor.
** UPDATE: **
Syslog reports the following entries:
kernel: [18790.510656] audit: type=1400 audit(146069817
kernel: [18791.184460] audit: type=1400 audit(146069817
kernel: [18791.697212] audit: type=1400 audit(146069817
kernel: [18792.402319] audit: type=1400 audit(146069817
kernel: [18792.940413] audit: type=1400 audit(146069817
kernel: [18868.825379] audit: type=1400 audit(146069825
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: tor 0.2.7.6-1ubuntu1
ProcVersionSign
Uname: Linux 4.4.0-17-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Apr 10 10:19:11 2016
InstallationDate: Installed on 2015-12-22 (109 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: tor
UpgradeStatus: Upgraded to xenial on 2016-04-07 (2 days ago)
modified.
modified.
mtime.conffile.
mtime.conffile.
Changed in tor (Ubuntu): | |
importance: | Undecided → Medium |
Changed in tor (Debian): | |
status: | Unknown → Fix Released |
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.