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 http://deb.torproject.org/torproj
On Sat, Apr 19, 2014 at 10:42 PM, kbesig wrote:
> 2. As root: /usr/bin/vidalia
>
> No protocol specified
> vidalia: cannot connect to X server :0
>
I am not sure if you should be running vidalia as root, but if you wish to
test:
1. Open a terminal before you switch to root
2.
xhost lo
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) Vida
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 AppArmo
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
I'll give your suggestion, "tor-arm", a try.
On 04/19/2014
On Sat, Apr 19, 2014 at 11:46 PM, kbesig 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): GConf-WARNING
Sorry for the spam in advance..
Install of tor-arm went well enough, no error msg's.
~$ sudo -u debian-tor arm
Traceback (most recent call last):
File "/usr/share/arm/starter.py", line 578, in
cli.controller.startTorMonitor(time.time() - initTime)
File "/usr/share/arm/cli/controller.py
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
Desc
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",
Getting closer:
I can run tor arm as root, but get this error as :
~$ sudo -u debian-tor arm
[sudo] password for :
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 enough, n
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 HashedControlPa
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.
On 4/19/2014 4:16 PM, Roger Dingledine wrote:
> 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
Thanks for pointing this 'unsafe' use of arm out guys - I just checked and
it somehow snuck into my Pi relay tutorial docs also. I'll update them when
I have had chance to do some testing early next week.
Best,
Chris
On 19 Apr 2014 21:50, "Michael Wolf" wrote:
> On 4/19/2014 4:16 PM, Roger Ding
>>>
> 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 use
kbesig:
> Getting closer:
> I can run tor arm as root, but get this error as :
> ~$ sudo -u debian-tor arm
> [sudo] password for :
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:
Relay's up and running using arm , both running as .
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
https://lists.torproject.org/cgi-bin/m
On Sun, 20 Apr 2014 15:19:57 +0200
Lunar allegedly wrote:
> kbesig:
> > Getting closer:
> > I can run tor arm as root, but get this error as :
> > ~$ sudo -u debian-tor arm
> > [sudo] password for :
>
> Urg… please never do that. You should not run applications with the
> same privileges as Tor.
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,
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?
'group
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?
'group
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/30/2014 11:38 AM, Delton Barnes wrote:
> 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 #1
On 2014-04-30 20:38, Delton Barnes wrote:
Followed item #14, but after logging out/in I get:
$ arm
Connection refused. Is the ControlPort enabled?
'groups' shows the 'debian-tor' group. 'sudo -u debian-tor arm' still
works. Anyone have an idea what I've missed?
Does the "debian-tor" gr
Kurt Besig:
> Also be sure to un-comment the ControlPort and assign an ip to it if
> different that default in your /etc/torrc.
Alexander Dietrich:
> Does the "debian-tor" group have access to the file
> "/var/run/tor/control.authcookie"?
Thanks, Kurt & Alexander. I had not enabled the ControlP
24 matches
Mail list logo
