This is all just too much risk and admin on my production server on Linode.
Abacustard relay is down until I can move my production server,
downgrade the current linode and relegate it to backup functionality and
Tor exit node.
Cheers for now,
JB
On 18/11/2014 18:45, Zack Weinberg wrote
;s frowned upon.
Slippery slope slippery slopes
On 07/06/2014 10:28, Michael Wolf wrote:
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 e
Hi All,
FP! :)
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.
But it's also listed on http://cbl.abuseat.org/lookup.cgi?ip=5.104.224.5
as infected (or NATting
