9 left
And one more added, so 8 left.
+1 = 7 left
Added one. 6 left.
4 left.
+1, 3 left
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi DiffieHellman,
The solution is to disable password auth and use pubkeys only (so bruteforcing
attacks won't succeed until after the universe burns out), too bad most of the
bots are incompetently programmed and keep
retrying with a password even if the sshd returns that such auth method is
Hello,
I run several Linux root servers, spread over several providers, some of which
serve as Tor relays. For a few weeks now I have been observing massive brute
force attempts via SSH from hundreds of sources around the world. However, only
the Tor relays are affected, the rest of the server
Hi,
And as further proof (if any were needed) that watchdogcyberdefense.com
is run by bozos one of their "abuse" reports to Hetzner reportedly shows
a “log entry” which reported attacks from my IP address to the RFC 1918
address 192.168.200.216. That address, like all such 192.168/16 prefix
addr
contexts, and
will take no more than 5-10 minutes to finish.
You can learn more and take the survey at this link:
https://mit.co1.qualtrics.com/jfe/form/SV_6W3YXSCnqMVGPs1
Your input is very valuable to our study, and we look forward to your
feedback.
Please feel free to email us at anon-resea
Roger say it right: No exit relay at home!
I write this mail in anon because I had bad experience with that. I had
the experience to get visitors early in the morning from the police
department some months ago. After that I must by new computers...
Use ISP's only for exits. Or you want