-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
> https://github.com/nusenu/relayor
I'm sorry if you are looking for the repo,
github decided to hide my account from the public..
(without sending an email notification about anything)
"
One of our mostly harmless robots seems to think you are not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
computers are better at doing repeatable things over and over again so
let them take care of boring tasks.
Based on David's ansible-tor [1] I created an ansible role to make
relay operations more convenient (see the initial commit message for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ondrej Mikle:
>> I just filed two tickets to add support for multiple tor
>> instances to the official deb/rpm packages.
>>
>> I think this is useful for many relay operators (so they don't
>> have to replace the init scripts themselves anymore).
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I'm not a big fan of adding more complexity to "impove" security.
With fail2ban [1] you run the risk of, for example, someone
bruteforcing your ssh from every exit node they can find, then your
relay blocking those exits meaning there are certain ci
t; 53
>
> Don't forget to provide the fingerprint for others to investigate.
:)
>
>
> Matt
> --
> Speak Freely
>
>
> ***
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://list
tps://atlas.torproject.org/#details/BDE26705D49CB8AC3297953BCC2070FED9C611
> 53
>
> Don't forget to provide the fingerprint for others to investigate. :)
>
>
> Matt
> --
> Speak Freely
>
>
> ***
>
> ___
> t
Your relay is running 14 days now. You are pushing through more than
2,5 MBit/s (325.79 KB/s atm) That is great! Thanks, keep on doing that.
Whats your max upload MBit/s? If its 2,5 MBit/s your already maxing out
your connection.
On Sun, February 22, 2015 13:38, Volker Mink
wrote:
Finge
