Re: [tor-relays] Relay down, rejected, help

2014-04-30 Thread Delton Barnes
Roger Dingledine: You're using arm dangerously. See item #14 on https://www.torproject.org/docs/tor-relay-debian for the safer way to run arm with your Debian / Ubuntu relay. Followed item #14, but after logging out/in I get: $ arm Connection refused. Is the ControlPort enabled? 'groups'

Re: [tor-relays] Relay down, rejected, help

2014-04-21 Thread Roger Dingledine
On Sat, Apr 19, 2014 at 02:15:52PM -0800, I wrote: Wow, I always thought that *was* the safe way to run arm. I wonder where we both got the advice to do it the dangerous way. from ARM [ARM_NOTICE] Arm is currently running with root permissions. This is not a good idea, and will

Re: [tor-relays] Relay down, rejected, help

2014-04-20 Thread Lunar
kbesig: Getting closer: I can run tor arm as root, but get this error as user: ~$ sudo -u debian-tor arm [sudo] password for user: Urg… please never do that. You should not run applications with the same privileges as Tor. What you want is to add your current user to the “debian-tor” group:

Re: [tor-relays] Relay down, rejected, help

2014-04-20 Thread kbesig
Relay's up and running using arm , both running as user. A big thank you to all who responded with suggestions all of which lead to a successful conclusion! ___ tor-relays mailing list tor-relays@lists.torproject.org

Re: [tor-relays] Relay down, rejected, help

2014-04-20 Thread mick
On Sun, 20 Apr 2014 15:19:57 +0200 Lunar lu...@torproject.org allegedly wrote: kbesig: Getting closer: I can run tor arm as root, but get this error as user: ~$ sudo -u debian-tor arm [sudo] password for user: Urg… please never do that. You should not run applications with the same

[tor-relays] Relay down, rejected, help

2014-04-19 Thread kbesig
My relay became one of the rejected since the heartbleed vulnerability surfaced so I reformatted my XP relay and did a fresh Ubuntu 14.04 LTS install. Built vidalia-0.2.21 from source using: deb http://deb.torproject.org/torproject.org trusty main deb-src

Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread irregulator
On 04/19/2014 05:42 PM, kbesig wrote: My relay became one of the rejected since the heartbleed vulnerability surfaced so I reformatted my XP relay and did a fresh Ubuntu 14.04 LTS install. Built vidalia-0.2.21 from source using: I would suggest completely avoiding (the burden of) Vidalia.

Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread kbesig
Yes, thanks for the concern regarding root, I was doing so for test purposes only. :/usr/bin$ xhost local:root non-network local connections being added to access control list :/usr/bin$ /usr/bin/vidalia (process:1341): GConf-WARNING **: Client failed to connect to the D-BUS daemon: An

Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread kbesig
Thanks for that, Alex, I had no problems installing Tor and have been starting the gui using the shell script : ~/Tor/tor-browser_en-US$ sh start-tor-browser Launching Tor Browser Bundle for Linux in /home/user/Tor/tor-browser_en-US yada-yada I'll give your suggestion, tor-arm, a try. On

Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread Sanjeev Gupta
On Sat, Apr 19, 2014 at 11:46 PM, kbesig kbe...@socal.rr.com wrote: Yes, thanks for the concern regarding root, I was doing so for test purposes only. :/usr/bin$ xhost local:root non-network local connections being added to access control list :/usr/bin$ /usr/bin/vidalia (process:1341):

Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread David Serrano
On 2014-04-19 09:19:26 (-0700), kbesig wrote: OSError: [Errno 13] Permission denied: '/home/user/.arm/' Any ideas?? Delete /home/user/.arm. It will be created again. Did you run it as root first? That would explain this problem. -- David Serrano GnuPG id: 280A01F9 signature.asc

Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread Luther Blissett
On Sat, 2014-04-19 at 07:42 -0700, kbesig wrote: 1. As non-admin: /usr/bin/vidalia (process:540): GConf-WARNING **: Client failed to connect to the D-BUS daemon: An AppArmor policy prevents this sender from sending this message to this recipient, 0 matched rules; type=method_call,

Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread kbesig
Getting closer: I can run tor arm as root, but get this error as user: ~$ sudo -u debian-tor arm [sudo] password for user: Connection refused. Is the ControlPort enabled? Where is arm's config? On 04/19/2014 09:19 AM, kbesig wrote: Sorry for the spam in advance.. Install of tor-arm went well

Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread Jodie Miu
Enable the ControlPort in your torrc file by uncommenting it, and setup authentication to the ControlPort in one of two ways: HashedControlPassword or CookieAuthentication. To enable CookieAuthentication, simply remove the hash sign in front of that line. I can't remember how to do

Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread Roger Dingledine
On Sat, Apr 19, 2014 at 09:19:26AM -0700, kbesig wrote: Install of tor-arm went well enough, no error msg's. ~$ sudo -u debian-tor arm You're using arm dangerously. See item #14 on https://www.torproject.org/docs/tor-relay-debian for the safer way to run arm with your Debian / Ubuntu relay.

Re: [tor-relays] Relay down, rejected, help

2014-04-19 Thread I
Wow, I always thought that *was* the safe way to run arm. I wonder where we both got the advice to do it the dangerous way. from ARM [ARM_NOTICE] Arm is currently running with root permissions. This is not a good idea, and will still work perfectly well if it's run with the same user as