Dear all,
Previously, I've run arm using 'sudo -u debian-tor arm'. As was mentioned here previously, this is not how you should run it - in fact there is a bit of documentation to suggest how it should be done. Unfortunately I'm having some issues getting arm working correctly as described here in step 14:
https://www.torproject.org/docs/tor-relay-debian.html.en#after
Having added my user (pi) to the debian-tor group, I try to run 'arm' and get the following:
Failed to read authentication cookie (permission denied): /var/run/tor/control.authcookie
I've tried reinstalling arm, relogged and checked that I'm in the right group still using 'groups' (which I am) - no joy.
I've checked my torrc and found the following lines:
## If you enable the controlport, be sure to enable one of these ## authentication methods, to prevent attackers from accessing it. #HashedControlPassword 16:872860B76453A77D60CA2BB8C1A7042072093276A3D701AD684053EC4C #CookieAuthentication 1
CookieAuthentication wasn't initially enabled, turning it on makes no difference, I get the same error.
I am able to get it working when setting up HashedControlPassword by generating a has using tor --hash-password <password> and editing torrc accordingly.
Am I missing something when it comes to setting up CookieAuthentication? I guess I must be...although it seems strange that I was getting that error even with CookieAuthentication disabled.
Any insight appreciated :)
Chris
On Mon, 22 Sep 2014 21:34:40 +0100 Chris Whittleston csw34@cam.ac.uk wrote:
Am I missing something when it comes to setting up CookieAuthentication? I guess I must be...although it seems strange that I was getting that error even with CookieAuthentication disabled.
Any insight appreciated :)
The configuration file "tor-service-defaults-torrc" in /usr/share/tor directory is read as well as /etc/tor/torrc file. It is used as a default configuration and CookieAuthentication is enabled in that file. You may want to take a look at that :)
Regards, Grace H.
Aha - thanks Grace, that explains the initial error for sure!
Chris
On 22 September 2014 21:53, Grace H. grace@mail2tor.com wrote:
On Mon, 22 Sep 2014 21:34:40 +0100 Chris Whittleston csw34@cam.ac.uk wrote:
Am I missing something when it comes to setting up CookieAuthentication? I guess I must be...although it seems strange that I was getting that error even with CookieAuthentication disabled.
Any insight appreciated :)
The configuration file "tor-service-defaults-torrc" in /usr/share/tor directory is read as well as /etc/tor/torrc file. It is used as a default configuration and CookieAuthentication is enabled in that file. You may want to take a look at that :)
Regards, Grace H.
-- D8C9 EF71 ADC3 0533 29DE 3A80 1152 D1CB 8D9C 47FD
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Mon, Sep 22, 2014 at 09:34:40PM +0100, Chris Whittleston wrote:
Previously, I've run arm using 'sudo -u debian-tor arm'. As was mentioned here previously, this is not how you should run it - in fact there is a bit of documentation to suggest how it should be done.
Yep. See https://trac.torproject.org/projects/tor/ticket/10700 for the discussion.
Unfortunately I'm having some issues getting arm working correctly as described here in step 14:
https://www.torproject.org/docs/tor-relay-debian.html.en#after
Having added my user (pi) to the debian-tor group, I try to run 'arm' and get the following:
Failed to read authentication cookie (permission denied): /var/run/tor/control.authcookie
What Tor version are you using? There was a bug in Tor 0.2.5.1-alpha through 0.2.5.6-alpha that broke cookie auth for this situation: https://trac.torproject.org/projects/tor/ticket/12864 It is fixed in 0.2.5.7-rc.
I've tried reinstalling arm, relogged and checked that I'm in the right group still using 'groups' (which I am) - no joy.
CookieAuthentication wasn't initially enabled, turning it on makes no difference, I get the same error.
As Grace pointed out, torrc isn't the only config file that your Tor deb uses.
Am I missing something when it comes to setting up CookieAuthentication? I guess I must be...although it seems strange that I was getting that error even with CookieAuthentication disabled.
If the Tor version hint doesn't do it for you, I'm not sure what the next step is. Hopefully it does. :)
--Roger
Haha - yes I am indeed running 0.2.5.6, that would explain the cookie issue.
It seems that I've had a GPG key issue which has stopped me updating to 0.2.5.7-rc previously, but I've just noticed the new instructions here:
https://www.torproject.org/docs/debian.html.en#ubuntu
It looks like installing deb.torproject.org-keyring will help prevent those issues in the future.
I'll update my Pi relay tutorial with this and the updated arm instructions
https://docs.google.com/document/d/1bf_D_j1O-9ckTS9DY8ngIdiFwHta6Q5Uj_5dvOia...
Thanks again both,
Chris
On 22 September 2014 22:15, Roger Dingledine arma@mit.edu wrote:
On Mon, Sep 22, 2014 at 09:34:40PM +0100, Chris Whittleston wrote:
Previously, I've run arm using 'sudo -u debian-tor arm'. As was mentioned here previously, this is not how you should run it - in fact there is a
bit
of documentation to suggest how it should be done.
Yep. See https://trac.torproject.org/projects/tor/ticket/10700 for the discussion.
Unfortunately I'm having some issues getting arm working correctly as described here in step 14:
https://www.torproject.org/docs/tor-relay-debian.html.en#after
Having added my user (pi) to the debian-tor group, I try to run 'arm' and get the following:
Failed to read authentication cookie (permission denied): /var/run/tor/control.authcookie
What Tor version are you using? There was a bug in Tor 0.2.5.1-alpha through 0.2.5.6-alpha that broke cookie auth for this situation: https://trac.torproject.org/projects/tor/ticket/12864 It is fixed in 0.2.5.7-rc.
I've tried reinstalling arm, relogged and checked that I'm in the right group still using 'groups' (which I am) - no joy.
CookieAuthentication wasn't initially enabled, turning it on makes no difference, I get the same error.
As Grace pointed out, torrc isn't the only config file that your Tor deb uses.
Am I missing something when it comes to setting up CookieAuthentication?
I
guess I must be...although it seems strange that I was getting that error even with CookieAuthentication disabled.
If the Tor version hint doesn't do it for you, I'm not sure what the next step is. Hopefully it does. :)
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
FWIW, I had similar aspirations except the Raspberry Pi's aren't able to push out more than 1-2Mb so I just ran it as a bridge.
Here are some precompiled DEB's for the RBP: https://github.com/antitree/tor-deb-raspberry-pi (not saying you should trust me) Here are some of the build scripts and a little Text-based GUI for configuring a relay and other stuff: https://github.com/antitree/tor-raspberry-pi-build-scripts/blob/master/scrip...
On Mon, Sep 22, 2014 at 5:37 PM, Chris Whittleston csw34@cam.ac.uk wrote:
Haha - yes I am indeed running 0.2.5.6, that would explain the cookie issue.
It seems that I've had a GPG key issue which has stopped me updating to 0.2.5.7-rc previously, but I've just noticed the new instructions here:
https://www.torproject.org/docs/debian.html.en#ubuntu
It looks like installing deb.torproject.org-keyring will help prevent those issues in the future.
I'll update my Pi relay tutorial with this and the updated arm instructions
https://docs.google.com/document/d/1bf_D_j1O-9ckTS9DY8ngIdiFwHta6Q5Uj_5dvOia...
Thanks again both,
Chris
On 22 September 2014 22:15, Roger Dingledine arma@mit.edu wrote:
On Mon, Sep 22, 2014 at 09:34:40PM +0100, Chris Whittleston wrote:
Previously, I've run arm using 'sudo -u debian-tor arm'. As was
mentioned
here previously, this is not how you should run it - in fact there is a
bit
of documentation to suggest how it should be done.
Yep. See https://trac.torproject.org/projects/tor/ticket/10700 for the discussion.
Unfortunately I'm having some issues getting arm working correctly as described here in step 14:
https://www.torproject.org/docs/tor-relay-debian.html.en#after
Having added my user (pi) to the debian-tor group, I try to run 'arm'
and
get the following:
Failed to read authentication cookie (permission denied): /var/run/tor/control.authcookie
What Tor version are you using? There was a bug in Tor 0.2.5.1-alpha through 0.2.5.6-alpha that broke cookie auth for this situation: https://trac.torproject.org/projects/tor/ticket/12864 It is fixed in 0.2.5.7-rc.
I've tried reinstalling arm, relogged and checked that I'm in the right group still using 'groups' (which I am) - no joy.
CookieAuthentication wasn't initially enabled, turning it on makes no difference, I get the same error.
As Grace pointed out, torrc isn't the only config file that your Tor deb uses.
Am I missing something when it comes to setting up
CookieAuthentication? I
guess I must be...although it seems strange that I was getting that
error
even with CookieAuthentication disabled.
If the Tor version hint doesn't do it for you, I'm not sure what the next step is. Hopefully it does. :)
--Roger
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- *Dr Chris Whittleston 栗主* Department of Chemistry University of Cambridge Lensfield Road, Cambridge, CB2 1EW Email: csw34@cam.ac.uk Tel: +44 (0)1223 336423
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
tor-relays@lists.torproject.org
-
AntiTree -
Chris Whittleston -
Grace H. -
Roger Dingledine