Hi Jesse,
Yes, a very large amount of nodes were rejected from the network for
running vulnerable versions.
Relevant threads :
* https://lists.torproject.org/pipermail/tor-relays/2014-April/004336.html
* https://lists.torproject.org/pipermail/tor-relays/2014-April/004340.html
Tom
Jesse Vi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hey everyone,
I just checked in on https://metrics.torproject.org/network.html and
noticed that there's been sudden drops in the number of relays which
seems to have caused all other graphs to tank as well. It's too late for
this drop to be caused
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.
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
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:
On 4/19/2014 4:50 PM, Michael Wolf wrote:
> It's worth noting that, under Debian (Jessie, others?), arm will be
> unable to read tor's logs if you run it as your user. The default group
> for /var/log/tor is 'adm'. You'll have to:
>
> $ sudo chgrp -R debian-tor /var/log/tor
>
> This will make t
