Re: [tor-relays] Got my first abuse

[Jason Odoom]

Running an Exit  node from home is asking for trouble. I can't imagine why
anyone would want to. Anyways, /etc/hosts.allow and /etc/hosts.deny can
also be used to limit SSH access. I highly recommend.

Best,
Jason

Sent from my Android device. Please excuse my brevity and any typos that
may occur.

On Thu, Apr 16, 2020, 3:32 PM Volker Mink  wrote:

> Not 100% accurate.
> I was running an exit at my home connection for close to one year. I
> removed it because normal internet usage became absolutely anoying. Capchas
> and DOS-Protections nearly everywhere. No streaming-portal was running. And
> lots of complaints from my provider.
> But no Cop action!
>
> And now i am running 2 exits hosted in datacenters, one in germany, one in
> malaysia. No problems by now.
>
>
> br,
> volker
>
>
> *Gesendet:* Donnerstag, 16. April 2020 um 13:32 Uhr
> *Von:* "NOC" 
> *An:* tor-relays@lists.torproject.org
> *Betreff:* Re: [tor-relays] Got my first abuse
> They raid your home even if the Tor node is run in a datacenter. Sadly
> the police in germany is still stuck in the 90s and most of them don't
> know and/or care what Tor is and how it works.
>
> On 16.04.2020 12:45, Mario Costa wrote:
> > Where you running an exit from home? It’s really discouraged because of
> what happened to you.
> >
> > -m
> >
> >> Il giorno 16 apr 2020, alle ore 04:50, Kolja Sagorski <
> ha...@koljasagorski.de> ha scritto:
> >>
> >> I had a police house search for my exit...
> >> I hate the stupid German police.
> >>
> >>> Am 15.04.2020 um 22:53 schrieb "li...@for-privacy.net" <
> li...@for-privacy.net>:
> >>>
> >>> Hi,
> >>>
> >>> my Family¹ has had an exit for 2 weeks and today the first abuse mail
> has arrived.
> >>>
> >>> First of all, thanks for the templates:
> >>>
> >>> https://www.torservers.net/wiki/abuse/templates
> >>>
> >>> https://trac.torproject.org/projects/tor/wiki/doc/TorAbuseTemplates
> >>>
> >>>
> >>> I linked these two from the Tor-project:
> >>>
> >>> - Common Boilerplate (Tor Intro)
> >>>
> >>> - SSH Bruteforce Attempts
> >>>
> >>> and wrote the following myself:
> >>> --
> >>> Another good option that we use ourselves is: fail2ban
> >>> And report to blacklists, which can then be loaded into the router
> firewalls:
> >>> https://www.abuseipdb.com/user/33280
> >>>
> >>> Hope this helps!
> >>> --
> >>>
> >>> I actually wanted to add that the SSH login attempts can be limited.
> (3-6)
> >>> Because the logs from the abuse mail showed 100 attempts pro IP. ;-)
> >>>
> >>> _Are such notes useful or do such instructions cause even more
> problems?_
> >>>
> >>>
> >>>
> >>> ¹https://metrics.torproject.org/rs.html#search/TorOrDie4privacyNET
> >>>
> >>> --
> >>> ╰_╯ Ciao Marco!
> >>>
> >>> Debian GNU/Linux
> >>>
> >>> It's free software and it gives you freedom!
> >>> ___
> >>> tor-relays mailing list
> >>> tor-relays@lists.torproject.org
> >>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> >> ___
> >> tor-relays mailing list
> >> tor-relays@lists.torproject.org
> >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> > ___
> > tor-relays mailing list
> > tor-relays@lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Turning down my relay from DigitalOcean

[Jason Odoom]

Good to know. I will consider these alternatives.

Best,
Jason

On Tue, Jul 3, 2018, 1:21 AM Mirimir  wrote:

> On 07/02/2018 06:41 AM, Jason Odoom wrote:
> > Guillermo,
> >
> > Sorry to read you've also had an issue with this. Please do share if you
> > are able to find a host that is open to allowing Tor Exit nodes!
> >
> > Best,
> > Jason
>
> GigaTux has said that they allow Tor exits.
>
> And they run one themselves:
>
> https://metrics.torproject.org/rs.html#details/2AB0B91CCF12664D5D95083A6A7B871918C8CF9C
>
> > On Mon, Jul 2, 2018, 9:28 AM Guillermo Narvaez 
> wrote:
> >
> >> Hello everyone,
> >>
> >> Sadly I'm stoping the tor daemon in my relay due high cost of bandwidth
> >> ($100), in the meantime I start to search an optional hosting.
> >>
> >> My apologies!
> >> -Guillermo
> >> ___
> >> tor-relays mailing list
> >> tor-relays@lists.torproject.org
> >> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> >>
> >
> >
> >
> > ___
> > tor-relays mailing list
> > tor-relays@lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> >
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Turning down my relay from DigitalOcean

[Jason Odoom]

Hello Vadim,

How long have you been running a relay with OVH? I know they've stated that
they do not allow Tor relays on their network.

Best,
Jason

On Mon, Jul 2, 2018, 11:06 AM Vadim Tsesko  wrote:

> Hello everybody,
>
> I am using OVH.ie for my Tor relay. They don't limit traffic.
>
> Good luck!
>
> On 07/02/2018 04:41 PM, Jason Odoom wrote:
> > Guillermo,
> >
> > Sorry to read you've also had an issue with this. Please do share if you
> > are able to find a host that is open to allowing Tor Exit nodes!
> >
> > Best,
> > Jason
> >
> >
> > On Mon, Jul 2, 2018, 9:28 AM Guillermo Narvaez  > <mailto:guille...@nrvz.net>> wrote:
> >
> > Hello everyone,
> >
> > Sadly I'm stoping the tor daemon in my relay due high cost of
> > bandwidth ($100), in the meantime I start to search an optional
> hosting.
> >
> > My apologies!
> > -Guillermo
> > ___
> > tor-relays mailing list
> > tor-relays@lists.torproject.org  tor-relays@lists.torproject.org>
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> >
> >
> >
> > ___
> > tor-relays mailing list
> > tor-relays@lists.torproject.org
> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> >
>
> --
> Best regards,
>Vadim Tsesko
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Turning down my relay from DigitalOcean

[Jason Odoom]

Guillermo,

Sorry to read you've also had an issue with this. Please do share if you
are able to find a host that is open to allowing Tor Exit nodes!

Best,
Jason


On Mon, Jul 2, 2018, 9:28 AM Guillermo Narvaez  wrote:

> Hello everyone,
>
> Sadly I'm stoping the tor daemon in my relay due high cost of bandwidth
> ($100), in the meantime I start to search an optional hosting.
>
> My apologies!
> -Guillermo
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Tor Exit Node Winter Shutdown

[Jason Odoom]

Thanks Paul. I will be sure to keep a backup.

Best,
Jason

- Jason Odoom
GPG 9031B50D


On Thu, Jun 28, 2018 at 6:55 PM Paul Templeton  wrote:

>
> > I regret to inform you all that I will be shutting down my Tor Exit
> node  - Winter [0] after more than five years.
>
> Makes me sad :-(
>
> Keep a backup - you may find hope else where... You never know.
>
> P
>
>
> 609662E824251C283164243846C035C803940378
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Tor Exit Node Winter Shutdown

[Jason Odoom]

Hello relay operators,

I regret to inform you all that I will be shutting down my Tor Exit node  -
Winter [0] after more than five years.  Digital Ocean's new bandwidth
policy has made it incredibly expensive to keep this online. I incurred
almost $200 of usage. I was lucky enough to have received a deduction off
of my bill. I also believe that in this case asking for donations will do
little to help. I did not host this Exit node for accolade but because I
truly believe in what the Tor project is doing. I will allocate my budget
for the Exit node towards monthly contributions to Tor as an alternative.
Hopefully in the future I will be able to return. It's been fun.

0:
https://metrics.torproject.org/rs.html#details/9EC5E097663862DF861A18C32B37C5F82284B27D

Best,
Jason

- Jason Odoom
GPG 9031B50D
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] how to distribute pgp public key?

[Jason Odoom]

On Dec 7, 2016 1:28 AM, "Univibe"  wrote:

If I want to include a reference to my public PGP key on Atlas using the
ContactInfo field on my relays, what's the best way to do it? Should I
upload my key to some of the public keyservers and then list the
fingerprint on Atlas?


Yes. I use the MIT Keyserver at http://pgp.mit.edu

If so which keyservers are recommended?

I had a thought to publish it on my relay's DirPort (using DirPortFrontPage
and a simple html doc containing the public key). Then I could just provide
a link to the DirPort in ContactInfo.


It's better to just use a fingerprint. I don't know how efficient or useful
that would be. It is also not necessary.


Is there a better way to do this?

___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Relays or exits: which is needed?

[Jason Odoom]

Hi Michael,

Exits are needed most.[1] But if you want to run an Exit be prepared to
deal with complaints. That link should answer your question in depth
although the stats are four years old. It also includes tips to make sure
you run an Exit with minor issues. Although the stats are outdated and the
percentage of Exits have increased over the years, as it states in the post
it is still one of the scarcest nodes. Hopefully others will be able to
provide more information concerning updated statistics. But I believe it
was covered at 30C3 last-year. [2]

Regards,

Jason Odoom

[1]
https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment
[2] http://youtube.com/watch?v=CJNxbpbHA-I

Sent from my Android, please excuse my brevity and any typos.
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] DigitalOcean starting Exit node crackdown

[Jason Odoom]

Hi Shawn,

 I also run an exit on DO's infrastructure and have been for the past six
months. I have received some complaints as well. Besides the usual
blacklisting, DO support has contacted me twice about my exit which I've
had to explain as well:

My email is not relevant to this IP address. There is no information in the
whois that identifies me. However, I am the owner and operator of
xxx.xxx.xxx. If you access that IP directly you can see that it is a Tor
Exit Router.

ln which I received the response:

We strongly recommend against running tor exit nodes on our droplets for
this reason. Please be aware that you are responsible for any abuse
generated from your droplet including that that comes across the Tor exit
node you are running. Failure to resolve these issues could result in
account suspension.

l responded assuring them I would take care of all issues. But for them to
shut down your exit is shocking. Were there any issues that needed
resolving that you ignored probably?

Regards,

Jason




On Thu, May 15, 2014 at 1:44 PM, Shawn Nock  wrote:

>
> Hello friends,
>
> As I recall, there are several exits running on DigitalOcean's
> infrastructure. This is presented FYI:
>
> Background: I've run an exit on DigitalOcean for about a year without
> issues (lost track of uptime duing heartbleed key regen). It wasn't
> hidden (the droplet name was 'tor-exit') and it had valid reverse DNS
> and the standard informational page was hosted there. At the time of
> droplet creation, tor exits were not prohibited by their ToS. I've
> mentioned to DigitalOcean staff during support tickets that it was a Tor
> exit.
>
> Today the exit was shutdown, the message received was this:
>
> >Hello
> >
> >We do see that you are running an exit node for the TOR network.
> >
> >Unfortunately we are unable to resume services to this droplet and ask
> >you that you please not run any other TOR exit nodes.
> >
> >Please get back to us as soon as possible so we can resolve this.
> >
> >Thanks
> >Support
>
> I sent the following response:
>
> >Hello,
> >
> >My droplet has been running for months (perhaps a year) with no
> >significant incidents. It is well managed, allows only a strict subset
> >of traffic to exit and the very few complaints that have been lodged
> >have been dealt with quickly and professionally (as said by your
> >support team). The droplet has been configured to limit the rate of
> >traffic below the droplet's monthly network transfer quota.
> >
> >It's well established that under US law ISPs are excluded from
> >liability under the safe-harbour provisions of the DCMA for any
> >copyright infringing traffic. More generally, the probability under US
> >law that an ISP would be held liable carrying user-generated traffic is
> >extremely low. Tor exits have been operated by Universities, Churches,
> >and corporations (large and small) for slightly more that 10
> >years. During this time not a single criminal or civil complaint has
> >been brought against an operator's ISP (to my knowledge).
> >
> >While it is surely your right to operate your business in the manner of
> >your choosing; I politely request an explanation for your apparent
> >policy against Tor exit nodes. If there is some way I might change the
> >parameters of the exit to suit a policy against specific traffic (to
> >certain IP blocks, port ranges); I'd surely comply.
> >
> >Finally, in this time where repressive regimes are cracking down on
> >Internet traffic and persecuting their countrymen and where free access
> >to the internet is nearing the stature of 'human right': if your policy
> >is indeed a general one against all Tor exits, I urge you to reconsider
> >your policy. It would be a great service to tens-of-thousands of Tor
> >users (refugees, political activists, religious minority, abused
> >spouses, law enforcement, &c) to revise your policy to allow
> >well-maintained exits to remain on your network.
> >
> >I appreciate any attention you could give to this serious matter.
>
> --
> n...@aphr.asia (OpenPGP: 0x6FDA11EE 3BC412E3)
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] any action required for AWS cloud relays?

[Jason Odoom]

Hi Lee,

 You should have received an email from AWS. Yes you definitely need to
take action. Here it is in case you missed it:

Dear Amazon EC2 Customer,

The OpenSSL project has recently announced a security vulnerability in
OpenSSL affecting versions 1.0.1 and 1.0.2 (CVE-2014-0160). Customers that
are running Linux and are using SSL could be affected by this issue and
should upgrade to a fixed version as soon as possible.

If you're using the Amazon Linux AMI, you can simply run "sudo yum update
openssl", and then restart any services using OpenSSL to protect any
at-risk instances.

Find more details and update instructions from the websites of your Linux
vendor of choice:
* Amazon Linux AMI:
https://aws.amazon.com/amazon-linux-ami/security-bulletins/ALAS-2014-320/
* Red Hat: https://rhn.redhat.com/errata/RHSA-2014-0376.html
* Ubuntu: http://www.ubuntu.com/usn/usn-2165-1/

Please note that several of the prominent Linux operating systems have
released fixed packages that still bear the OpenSSL 1.0.1e name.  Even
though the OpenSSL project released 1.0.1g as their newest software,
downstream Linux providers have in some cases elected to include just the
fix for CVE-2014-0160 in their packages in order to provide a small update
quickly. Updates to 1.0.1g are likely to come later.

For more information about this vulnerability, please visit
* AWS Security Bulletin page:
https://aws.amazon.com/security/security-bulletins/
* OpenSSL's official advisory:
https://www.openssl.org/news/secadv_20140407.txt
* The Heartbleed Bug: http://heartbleed.com/

Thank you,

AWS Security

Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is
a registered trademark of Amazon.com, Inc. This message was produced and
distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA
98109-5210

Regards,

Jason


On Wed, Apr 9, 2014 at 2:05 PM, lee colleton  wrote:

> Sorry, I mean this in light of CVE-2014-0160 the Heartbleed OpenSSL bug
>
>
> On Wed, Apr 9, 2014 at 11:04 AM, lee colleton  wrote:
>
>> I have relay(s) running in AWS. Will they auto-update? Do I need to take
>> any action?
>>
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] One relay shown as two relays in Atlas

[Jason Odoom]

Andy,

 I had the same problem a while ago, the non-active relay will soon
disappear. The relay with the three flags is currently not running so in
time it will no longer be displayed.

Regards,

Jason


On Thu, Jan 9, 2014 at 7:51 PM, I  wrote:

> Andy45,
>
> If you click on each of them are they both active?
> I've had one appear as two when it was reinstalled and Atlas took some
> time for the old version to disappear.
>
> after having a look
> The fingerprints are different so you may have done just that. Atlas will
> watch for a while then the older one will not appear.
>
> Robert
>
>
>
> > Here are my questions: I run a small exit relay on my computer.
> > (Nickname is Andy45 and IP address is 108.249.221.251 if you want to
> > look at this problem on Atlas for your self.)
> >
> > When I look up my relay on the Atlas, the relay is displayed as two
> > separate relays with differing bandwidths and different uptimes. I'm not
> > sure what's up with that - but my best guess is that it is splitting the
> > amount of bandwidth I donate in half? The one of the average bandwidths
> > listed on Atlas is a fair amount less than what the bandwidth monitor
> > shows I give. (70 kbps rather than 100+ kbps.)
> >
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Tor Weather getting T-shirt email. Problem

[Jason Odoom]

I agree there should be another way. I just recently had to start
overbecause
I updated Tor. I don't plan on updating again until two months have
passed.

Jason


On Mon, Dec 30, 2013 at 1:14 PM, Thomas Hand  wrote:

> I've run several middle relays for over a year but they keep getting
> knocked down due to circuit creation storms (on RPIs) or powercuts or
> updates or some other issue. Yes uptime is important, but 100% is not
> practical for most relay operators. Also, if you want a  shirt so badly,
> donate to Tor! In fact, I just realised I do want a shirt!
> Tom
>
>
> On 30 December 2013 11:48, Random Tor Node Operator <
> t...@unterderbruecke.de> wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 12/28/2013 01:26 AM, I wrote:
>> > I think two months is a bit short to be rewarded with a t-shirt
>> > from donated resources.
>> >
>> > It makes more sense to extend the time but include the total time
>> > running ignoring minor disruptions.
>>
>> I agree with that point, because currently, relay operators have the
>> incentive to not update to the latest Tor version whenever a new
>> version is released, in order to keep the consecutive uptime high.
>> That is probably not in the best interest of Tor.
>>
>> Maybe Tor Weather could look at the flags instead of the consecutive
>> uptime instead. For example, you typically don't lose your Guard or
>> Stable flag due to a reboot.
>>
>>
>>
>> >
>> > Robert
>> >
>> >
>> >> : i noticed a problem with tor weather. I should have recieved a
>> >> email : -Uptime is nearly 100%,
>> >>
>> >> Tor weather needs some updating, however it continues to email
>> >> plenty of relay operators. The reason you didn't get an email is
>> >> tor weather didn't see your relay matching the uptime
>> >> requirement,
>> >
>> >  GET
>> > FREE SMILEYS FOR YOUR IM & EMAIL - Learn more at
>> > http://www.inbox.com/smileys Works with AIM®, MSN® Messenger,
>> > Yahoo!® Messenger, ICQ®, Google Talk™ and most webmails
>> >
>> >
>> > ___ tor-relays mailing
>> > list tor-relays@lists.torproject.org
>> > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>> >
>>
>> -BEGIN PGP SIGNATURE-
>> Version: GnuPG v1.4.11 (GNU/Linux)
>> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>>
>> iQIcBAEBAgAGBQJSwV11AAoJEJe61A/xrcOQbPUP/RtgN4CQSJeUC8ZPt1/r0ryU
>> rc8ssBWHcmZBj513UaIes2HcmL72RMUXaaRtzDxrZR3F0gd7eRLWfBYXZw3M4XF+
>> 6SFVkesG2Mb5L41rRyqwHlIw/Cj9y9ilH6loQfAWDTaQJVtd9JQ8UQuVzIqTcAfd
>> /ZNJnC4lZGzmH+Iih0nS0hTb+NG9jEN/32pMFc4eh7fHDg4/A6TVKftHeAcjnnv1
>> eIeY8kOELT3U8Dd2OV0j8tpWbvC/Rz5KYnLA2EMQLdifhSMCtbXv0a3fr58Ph8JS
>> BfFKNFd+YvQNRUSPvkiUrCdjr8btPKYsNb9OPaNjUVkum6K1m8U/+z1OssdiGIxM
>> IDMKmxNpQ6xlmaaWh+KegVtvV/azo51PbMlj2f/8PmqAxeJokFBaHx5V07InaA62
>> OKtpcLhb3zrJNmLdjp2GQ5tuRJwnXc+B2ulCO1OtjWq3Snl04quMr6GL2IPbnUMB
>> UO8b3uN5tZp9IrO2rDTjlPLYNMLWhlgvaCKNpMDL83s1CzBJIzq2980fdd8KpSlY
>> ThTe2DfLM3uXgbHu77ff1NXLK9UCTQZ9jMhk7UUg9pPYpjeYIZwuB9F7fZN4lr/h
>> cdnFTJlo7P9n2MESfxzAshNg0fzSz3daTj524NnFvkl9W/ew+YqEocPkf/7Wn9xi
>> 2M2t1wC0QeFzdhMkXGqq
>> =IPcb
>> -END PGP SIGNATURE-
>> ___
>> tor-relays mailing list
>> tor-relays@lists.torproject.org
>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>>
>
>
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>
>
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays