On 6/6/2014 7:39 PM, JB wrote:
> I just setup my relay node today, and am keeping a hawkish(ish) eye on
> traffic And noticed a flurry of activity from SSH port (22) at
> 5.104.224.5 - which is listed as an exit.
That exit node uses port 22 as its ORPort (where other relays send Tor
traffic).
On 4/29/2014 6:06 PM, starlight.201...@binnacle.cx wrote:
> I just read that the relay can't get its
> old name back for six months now that
> the keys have been changed due to
> Heartbleed.
The "Named" flag is being done away with. Use your old nickname, or
whichever nickname you want... it won'
On 4/28/2014 10:04 PM, Zack Weinberg wrote:
> For what it's worth, after complaints from campus IT we also wound up
> blocking SSH in the CMU Tor exit's policy. It's a shame we can't help
> people do sysadmin stuff and whatnot anonymously, but the port scans
> do seem to happen quite often.
>
> z
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 deb
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
