Should be fixed by the recent SRU for Xenial (0.2.9.14-1ubuntu1~16.04.1)
and Artful (0.3.0.13-0ubuntu1~17.10.1).
** Changed in: tor (Ubuntu)
Status: Confirmed => New
** Changed in: tor (Ubuntu)
Status: New => Fix Committed
** Changed in: tor (Ubuntu)
Status: Fix Committed =>
** Bug watch added: Debian Bug tracker #867342
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867342
** Also affects: tor (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867342
Importance: Unknown
Status: Unknown
--
You received this bug notification because you
** Changed in: tor (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568435
Title:
Tor cannot start `obfs4proxy` ('Operation not permitted')
To manage n
Update:
the same issue exists with Ubuntu 14.04.5 and Ubuntu 15.10 when
installing tor from the "universe" repo.
Partial install log from Ubuntu 15.10
[...]
Setting up tor (0.2.6.10-1ubuntu2) ...
Something or somebody made /var/lib/tor disappear.
Creating one for you again.
Something or somebody
Sounds great!
Have you already made progress by any chance?
I am eagerly waiting for a fix! :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568435
Title:
Tor cannot start `obfs4proxy` ('Operatio
A fix would just have to be changing the apparmor profile that comes with the
tor package in Ubuntu.
I don't know how to do that, but I guess it would involve submitting a patch or
something. I'll try figure it out - it's such an easy fix, we just need someone
to put it into the repository.
--
** Bug watch added: Debian Bug tracker #822349
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822349
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568435
Title:
Tor cannot start `obfs4proxy` (
On Mon, 01 Aug 2016, Mark wrote:
> I do something like this now:
>
>
> sudo cp system_tor /etc/apparmor.d/system_tor
> sudo cp tor /etc/apparmor.d/abstractions/tor
>
> sudo apparmor_parser -r /etc/apparmor.d/system_tor
>
> sudo apt-get install tor
>
> It's a fine workaround.
>
>
> I wonder
@seanlano:
Thanks, reloading the the apparmor profile works!
I do something like this now:
sudo cp system_tor /etc/apparmor.d/system_tor
sudo cp tor /etc/apparmor.d/abstractions/tor
sudo apparmor_parser -r /etc/apparmor.d/system_tor
sudo apt-get install tor
It's a fine workaround.
I wonder
@guch9ux9cx, you'll need to reload the apparmor profile once you make the
change. You can do this with:
sudo apparmor_parser -r /etc/apparmor.d/system_tor
Or you can reboot - but on a LiveCD this will overwrite the change.
--
You received this bug notification because you are a member of Ubun
I think the problem is the 'P' flag - according to the reference
(http://wiki.apparmor.net/index.php/AppArmor_Core_Policy_Reference#Execute_rules)
this causes environment scrubbing, which obfs4proxy needs in order to
communicate with Tor.
--
You received this bug notification because you are a me
I think I am also affected by this.
In a live Ubuntu 16.04 (and 16.04.1) session I cannot get the tor service
running due to some apparmor restrictions (see dmesg logs someone else posted).
The updated apparmor profiles did not really fix my situation...
I think this should be upgrade to a defe
I am also affected by this, and I can confirm that making the change in
#6
(https://bugs.launchpad.net/ubuntu/+source/tor/+bug/1568435/comments/6)
fixes it (on Ubuntu 16.04).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
I confirm the suggested changes fix the issue for me.
Note:
the second path is wrong, correct path is /etc/apparmor.d/abstractions/tor (
the final `s` in `abstractions` is missed)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
Solution is to use the latest updated apparmor profile for tor
(/etc/apparmor.d/system_tor):
https://gitweb.torproject.org/debian/tor.git/tree/debian/tor.apparmor-profile
And in the Abstraction file (/etc/apparmor.d/abstraction/tor)
https://gitweb.torproject.org/debian/tor.git/tree/debian/tor.app
** Changed in: tor (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568435
Title:
Tor cannot start `obfs4proxy` ('Operation not permitted')
To manage notif
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: tor (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1568435
Title:
Tor ca
I have added the required infos into the bug descrition ( see the
section below 'UPDATE' )
** Description changed:
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
Can you report any apparmor rejections in syslog?
grep DENIED /var/log/syslog
This will help anybody tracking down what's going wrong here. Thanks.
** Tags added: apparmor
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
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 privile
20 matches
Mail list logo
