Re: [tor-relays] Emerald Onion's new relays

[Colin Childs]

Hi Christopher / Emerald,

This is all awesome news! 

Best of luck with your roll out, and please do not hesitate to reach out if 
there is anything we can do to assist you. 

I look forward to watching these relays come online!

> On Apr 1, 2019, at 11:36 PM, Christopher Sheats  
> wrote:
> 
> Hello,
> 
> Beginning this Wednesday, 2019-Apr-03, Emerald Onion will be starting 40 new 
> uncapped and unfiltered exit relays using HardenedBSD in Seattle. We will 
> turn on 10 new relays per day and be monitoring performance. In tandem, we 
> will be publishing our updated edge routing and Tor relay configurations on 
> our Github. We'll also publish an updated transparency report (spoiler: zero 
> new requests). This work is part of our efforts to saturate our new unmetered 
> 10Gbps transit link in the Westin data center. There we peer with the Seattle 
> Internet Exchange with a separate 10Gbps connection. We'll be using our 
> existing IP scopes:
> 
> 2620:18C::/36
> 23.129.64.0/24
> 
> We are in the process of creating an RPKI ROA for our prefixes, and we are 
> still rebuilding our DNS resolver (thanks nusenu for the feedback). These 
> things will be completed before we turn on the new relays.
> 
> If you donated to Emerald Onion (a 501(c)(3)) nonprofit), thank you! We'll be 
> naming the relays accordingly. We will still accept new donations for relay 
> naming rights-- email me directly for more information. Lastly, and If you're 
> unaware, I spoke about our work at DEFCON 26: 
> https://www.youtube.com/watch?v=cs6a1i4Owic
> 
> Cheers,
> 
> --
> Christopher Sheats
> Executive Director for Emerald Onion
> Email: yawn...@emeraldonion.org
> Office (& Signal): +1-206-739-3390
> Website: https://emeraldonion.org/
> 
> ___
> 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] IRC relay operator meetup - April 4th

[Colin Childs]

Hi everyone,

This is the announcement that we will be holding the April IRC relay operator 
meetup this Thursday, April 4th, at 22:00UTC in #tor-meeting on irc.oftc.net.

As usual, please add any agenda items to the pad below that you would like to 
discuss!

https://storm.torproject.org/shared/_595igXmpGkxq4FdyusPOI-6zzbvwzcodMl4hl2FVGu 
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] IRC meetup time poll

[Colin Childs]

Hello everyone,

Based on the feedback from the poll, the next meeting will take place on 
Thursday, April 4th @ 22:00UTC. 

I will send a reminder email out on April 1st with the agenda pad as usual.

Thanks for voting in the poll! 

> On Mar 13, 2019, at 7:32 PM, Colin Childs  wrote:
> 
> Hi everyone,
> 
> Just a friendly reminder that we will be closing this poll on Friday, so 
> please be sure you fill in your preferred times ASAP!
> 
> Currently, the most popular time appears to be 23:00UTC.
> 
> I hope you’re all having a great week! 
> 
>> On Mar 8, 2019, at 11:15 AM, Colin Childs > <mailto:co...@torproject.org>> wrote:
>> 
>> Hi everyone,
>> 
>> We are looking at changing the current IRC relay operator meetup time, as 
>> well as adding additional times throughout the month. 
>> 
>> I have created a poll at https://xoyondo.com/dp/oyUpcPqhnnJ6TWz 
>> <https://xoyondo.com/dp/oyUpcPqhnnJ6TWz> to collect time preferences for the 
>> next meetup (all times are GMT+0).
>> 
>> Please add your time preferences by March 15th (1 week from today) to help 
>> us better select times that work for you! 
>> 
>> Thanks, I hope you all have a great weekend! 
>> ___
>> tor-relays mailing list
>> tor-relays@lists.torproject.org <mailto: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] IFF relay operator meetup

[Colin Childs]

Hi everyone,

The Tor Project is hosting a relay operator meetup at the 2019 IFF[1]!

If you are attending the IFF, please join us on Wednesday, April 3rd @ 16:00 in 
Los Naranjos! We will discuss common issues operators face, as well as how we 
can all help to grow the relay operator community both locally and globally.

Note: Los Naranjos is inside the IFF venue. You will need to have a ticket for 
the IFF in order to attend this event.


[1] 
https://platform.internetfreedomfestival.org/en/IFF2019/public/schedule/custom/1468
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Cannot install obfs proxy in my Centos

[Colin Childs]

Hi Cuco,

It is possible that gitlab was experiencing some issues when you attempted to 
run this.

I’ve just confirmed that "go get 
git.torproject.org/pluggable-transports/obfs4.git/obfs4proxy 
” should 
build properly, and not result in a 404 as you were seeing. 

Could you please try installing again, and let us know if you are still seeing 
this? If you are, can you confirm you are able to ping gitlab.com 
? 

Thanks for your interest in running a bridge! 

> On Mar 20, 2019, at 10:51 AM, Cuco Cuquito  wrote:
> 
> 
> go get git.torproject.org/pluggable-transports/obfs4.git/obfs4proxy 
> 
> Not work
> 
> 
> 
> 
> On Wed, Mar 20, 2019 at 8:11 AM Volker Mink  > wrote:
> of course you can :)
> please follow this guide, scroll down https://www.torproject.org/docs/bridges 
> 
> If you want to help out, you should decide whether you want to run a normal 
> Tor relay or a bridge relay 
> . You can 
> configure your bridge either manually or graphically:
> 
> manually edit your torrc file 
>  to be just these four 
> lines:
> 
> SocksPort 0
> ORPort auto
> BridgeRelay 1
> Exitpolicy reject *:*
> 
>  
> When configured as a bridge, your server will not appear in the public Tor 
> network.
> 
> Your bridge relay will automatically publish its address to the bridge 
> authority, which will give it out via https or email as above. You can 
> construct the bridge address using the format above 
>  (you can find the 
> fingerprint in your Tor log files or in /var/lib/tor/fingerprint depending on 
> your platform).
> 
> If you would like to learn more about our bridge design from a technical 
> standpoint, please read the Tor bridges specification 
> . If 
> you're interested in running an unpublished bridge or other non-standard 
> uses, please do read the specification.
> 
>  
>  
> Gesendet: Mittwoch, 20. März 2019 um 14:05 Uhr
> Von: "George" mailto:geo...@queair.net>>
> An: tor-relays@lists.torproject.org 
> Betreff: Re: [tor-relays] Bridge relay
> Cuco Cuquito:
> > Can I run a bridge if I have only dynamic IP ?
> 
> Yes. Absolutely.
> 
> 
> --
> 
> 34A6 0A1F F8EF B465 866F F0C5 5D92 1FD1 ECF6 1682
> ___
> 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] IRC meetup time poll

[Colin Childs]

Hi everyone,

Just a friendly reminder that we will be closing this poll on Friday, so please 
be sure you fill in your preferred times ASAP!

Currently, the most popular time appears to be 23:00UTC.

I hope you’re all having a great week! 

> On Mar 8, 2019, at 11:15 AM, Colin Childs  wrote:
> 
> Hi everyone,
> 
> We are looking at changing the current IRC relay operator meetup time, as 
> well as adding additional times throughout the month. 
> 
> I have created a poll at https://xoyondo.com/dp/oyUpcPqhnnJ6TWz 
> <https://xoyondo.com/dp/oyUpcPqhnnJ6TWz> to collect time preferences for the 
> next meetup (all times are GMT+0).
> 
> Please add your time preferences by March 15th (1 week from today) to help us 
> better select times that work for you! 
> 
> Thanks, I hope you all have a great weekend! 
> ___
> 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] IRC meetup time poll

[Colin Childs]

Hi everyone,

We are looking at changing the current IRC relay operator meetup time, as well 
as adding additional times throughout the month. 

I have created a poll at https://xoyondo.com/dp/oyUpcPqhnnJ6TWz 
 to collect time preferences for the 
next meetup (all times are GMT+0).

Please add your time preferences by March 15th (1 week from today) to help us 
better select times that work for you! 

Thanks, I hope you all have a great weekend! ___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Monthly IRC operator meetup - March 7th

[Colin Childs]

Hi everyone,

This is a reminder that the next IRC relay operator meetup will be held on 
Thursday, March 7th at 02:00UTC.

These meetups take place on irc.oftc.net , in 
#tor-meeting.

We are also working on adding additional meetups throughout the month to better 
accommodate operators in different timezones, I hope to have more news about 
this shortly.

I hope you’re all having a great week!


Where: irc.oftc.net  @ #tor-meeting
When: Thursday, March 7th @ 02:00UTC
Agenda pad: 
https://storm.torproject.org/shared/7aCxQSwglBMGqO2o49g-_Iby9lDJgiaw8KLPL21fMmm 

 (please feel free to add discussion items)



signature.asc
Description: Message signed with OpenPGP
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] IRC operator meeting - February 7th

[Colin Childs]

Hello everyone,

I have an apology to make: 

When planning this meetup, I handled the timezone conversion incorrectly on my 
end and I intended for this to be held at 8:00PM CST (GMT-6) on Thursday, 
February 7th. This announcement should have read that the meetup is occurring 
on Friday, February 8th @ 02:00 UTC for it to match what I was intending at the 
time. I am very sorry to anyone who turned up a couple hours ago and had no one 
around to talk with, this was absolutely not my intent.

Going forward, we will be holding this meetup at 02:00UTC on the first Thursday 
of the month (as previously advertised), which means for people in North 
America it will be Wednesday evening. We are also looking into holding a second 
regular meetup each month at a time more appropriate for operators outside of 
North America; I should have more details for everyone regarding this in the 
next week. 

As I am aware many of you keep busy schedules and require some lead time for 
planning, we will hold the February meetup next week on Thursday, February 14th 
@ 02:00. After this meetup we will be going with the first Thursday of the 
month as previously advertised, which means the following meetup will be held 
March 7th @ 02:00 UTC. 

I apologize again for the confusion, I hope you are all having a good week. 

> On Feb 4, 2019, at 11:34 AM, Colin Childs  wrote:
> 
> Hi everyone,
> 
> As previously discussed 
> (https://lists.torproject.org/pipermail/tor-relays/2019-January/016894.html 
> <https://lists.torproject.org/pipermail/tor-relays/2019-January/016894.html>) 
> we are resuming our IRC relay operator meetings this Thursday, February 7th @ 
> 2:00UTC. 
> 
> These meetings will be held in #tor-meeting on irc.oftc.net 
> <http://irc.oftc.net/>. 
> 
> If you’d like to add to the agenda, please edit the pad at 
> https://storm.torproject.org/shared/mbyhs_ors7pdIxU92TLQoK_OzDGNpVw6p_zkC6Dy0U-
>  
> <https://storm.torproject.org/shared/mbyhs_ors7pdIxU92TLQoK_OzDGNpVw6p_zkC6Dy0U->
> 
> See you all there! 
> ___
> 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] IRC operator meeting - February 7th

[Colin Childs]

Hi everyone,

As previously discussed 
(https://lists.torproject.org/pipermail/tor-relays/2019-January/016894.html 
) 
we are resuming our IRC relay operator meetings this Thursday, February 7th @ 
2:00UTC. 

These meetings will be held in #tor-meeting on irc.oftc.net 
. 

If you’d like to add to the agenda, please edit the pad at 
https://storm.torproject.org/shared/mbyhs_ors7pdIxU92TLQoK_OzDGNpVw6p_zkC6Dy0U- 


See you all there! ___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] FOSDEM Relay Operator Meetup

[Colin Childs]

Hi everyone,

The meetup will be held on Sunday, February 3rd @ 15:00 in room H.3244.

I hope all of you at FOSDEM can make it! 

> On Jan 25, 2019, at 1:05 PM, Colin Childs  wrote:
> 
> Hello everyone,
> 
> We have put the current FOSDEM relay operator meet-up details at 
> https://blog.torproject.org/events/fosdem-brussels 
> <https://blog.torproject.org/events/fosdem-brussels>, I have also included 
> the text below:
> 
> — BEGIN POST ---
> 
> During FOSDEM 2019, the Tor Project will also be hosting a relay operator 
> meetup.
> 
> We will discuss common issues operators face, potential solutions, as well as 
> how we can all help to grow the relay operator community both locally and 
> globally. We'll be on hand to answer questions and want to hear your feedback 
> about the community, running relays, and what we can do to better support you.
>  
> The date, time, and location for the meetup will be posted the morning 
> (GMT+1) of February 2nd. We are aiming to hold this event on Sunday, February 
> 3rd; however we will not be able to book the room until FOSDEM begins.
>  
> We look forward to seeing you there.
> 
> --- END POST ——
> 
> Once we have confirmed the room on the morning of February 2nd, I will send a 
> follow-up email to this thread with the currently missing details. 
> 
> If you have any questions or concerns, please do not hesitate to reach out.
> 
>> On Jan 22, 2019, at 5:47 PM, Colin Childs > <mailto:co...@torproject.org>> wrote:
>> 
>> Hi everyone,
>> 
>> I just wanted to let everyone know I’ve seen this email, and will be 
>> responding in full shortly. 
>> 
>> There are a couple details still being worked out, and as soon as this is 
>> done I will update the list.
>> 
>> Thanks for your patience! 
>> 
>>> On Jan 19, 2019, at 2:31 PM, relaya relaya >> <mailto:rel...@mailbox.org>> wrote:
>>> 
>>> Hello! 
>>> I read there is a Relay Operator Meetup organized by Colin at. 
>>> 
>>> I'm surprised it has not been announced on this list yet. 
>>> 
>>> Where and when does it take place exactly? 
>>> 
>>> thank you! 
>>> ___
>>> tor-relays mailing list
>>> tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org>
>>> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
>> 
>> ___
>> tor-relays mailing list
>> tor-relays@lists.torproject.org <mailto: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] FOSDEM Relay Operator Meetup

[Colin Childs]

Hello everyone,

We have put the current FOSDEM relay operator meet-up details at 
https://blog.torproject.org/events/fosdem-brussels 
<https://blog.torproject.org/events/fosdem-brussels>, I have also included the 
text below:

— BEGIN POST ---

During FOSDEM 2019, the Tor Project will also be hosting a relay operator 
meetup.

We will discuss common issues operators face, potential solutions, as well as 
how we can all help to grow the relay operator community both locally and 
globally. We'll be on hand to answer questions and want to hear your feedback 
about the community, running relays, and what we can do to better support you.
 
The date, time, and location for the meetup will be posted the morning (GMT+1) 
of February 2nd. We are aiming to hold this event on Sunday, February 3rd; 
however we will not be able to book the room until FOSDEM begins.
 
We look forward to seeing you there.

--- END POST ——

Once we have confirmed the room on the morning of February 2nd, I will send a 
follow-up email to this thread with the currently missing details. 

If you have any questions or concerns, please do not hesitate to reach out.

> On Jan 22, 2019, at 5:47 PM, Colin Childs  wrote:
> 
> Hi everyone,
> 
> I just wanted to let everyone know I’ve seen this email, and will be 
> responding in full shortly. 
> 
> There are a couple details still being worked out, and as soon as this is 
> done I will update the list.
> 
> Thanks for your patience! 
> 
>> On Jan 19, 2019, at 2:31 PM, relaya relaya  wrote:
>> 
>> Hello! 
>> I read there is a Relay Operator Meetup organized by Colin at. 
>> 
>> I'm surprised it has not been announced on this list yet. 
>> 
>> Where and when does it take place exactly? 
>> 
>> thank you! 
>> ___
>> 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] FOSDEM Relay Operator Meetup

[Colin Childs]

Hi everyone,

I just wanted to let everyone know I’ve seen this email, and will be responding 
in full shortly. 

There are a couple details still being worked out, and as soon as this is done 
I will update the list.

Thanks for your patience! 

> On Jan 19, 2019, at 2:31 PM, relaya relaya  wrote:
> 
> Hello! 
> I read there is a Relay Operator Meetup organized by Colin at. 
> 
> I'm surprised it has not been announced on this list yet. 
> 
> Where and when does it take place exactly? 
> 
> thank you! 
> ___
> 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] community team highlights: Relay Advocacy

[Colin Childs]

Hello everyone,

As there is some concern / confusion about what occurred here, I wanted to take 
a moment to explain: 

After Nusenu discovered the cluster of relays on OVH not reporting contactinfo, 
I reached out to a contact we have at OVH to ask if they can pass along 
information to the user running these relays. This was in the hopes that the 
user may have configured things incorrectly by accident, and rather than 
immediately potentially marking the relays as bad; the hope was to give the 
user a chance to resolve the issue. OVH’s general abuse address was not 
contacted regarding this issue. 

That said, this did not end up resolving the issue and next steps will now need 
to be taken. 

I hope you all had a nice weekend. 

> On Jan 13, 2019, at 4:21 PM, niftybunny  wrote:
> 
> 
> 
>> On 13. Jan 2019, at 22:54, grarpamp  wrote:
>> 
 communicating with OVH regarding relays without contactinfo
>> 
>>> Is it *really* a good idea to poke OVH over this?
>>> in their ToS
>>> I feel this can backfire in a bad way
>>> is easier to ban all this "Tor" entirely?
>> 
>> Though there can be some context, in general
>> harassing and busywork for ISP is indeed not good.
>> Especially when Tor has recourse and discipline
>> of simply dropping the nodes from consensus
>> with log referral. That's the better way, nodes will
>> get clue eventually.
>> 
>> Another bettwer way is creating anti-Sybil web of trusts
>> and node selection meta metrics that operators and
>> users can contribute to and choose among. Which
>> is still an open project ripe and waiting since *years*
>> to be done by whoever wants to explore it.
> 
> I really need an ELI5 why this is a good idea. 
> 
> OVH is a European company, we have privacy laws here. When asking if you can 
> get the personal information for this servers you only will get a more or 
> less friendly FuckYou.
> And they have a CW fraction of 15%, if we nag them enough they may change 
> their TOS and start kicking all relays. This will be an even bigger nightmare 
> than DigitalOcean.
> 
> Let sleeping dogs lie.
> 
> Markus
> ___
> 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] AS: "OVH SAS" - 17 relays (2018-10-24)

[Colin Childs]

Hi Nusenu,

I have been in contact with OVH regarding these relays, and am currently 
waiting to hear back from someone in their abuse department. 

Thanks for bringing this to our attention! 

> On Dec 12, 2018, at 5:08 PM, nusenu  wrote:
> 
> Signed PGP part
> a relay gang joined in Oct 2018 at OVH
> 
> 
> 2018-10-24
> 
> |   Up |   Ext | JoinTime   | IP| CC   |   ORp |   Dirp | Version 
>   | Contact   | Nickname   |   eFamMembers | FP   
> |
> |--+---++---+--+---++---+---++---+--|
> |1 | 0 | 13:43:16   | 145.239.0.204 | de   |   443 |  0 | 0.3.4.8 
>   | None  | Chief  | 1 | 
> 5EF464D06322614A3B8B6C2652C3C616F098EE8A |
> |1 | 0 | 13:43:17   | 54.37.200.155 | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Dash   | 1 | 
> B55F8445569407FBE6BAF205799A9EF8AC8CC256 |
> |1 | 0 | 13:43:18   | 51.68.170.247 | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Rebel  | 1 | 
> E7B036D933D6E0A68983E8E3F664EAA54ACDEA37 |
> |1 | 0 | 13:43:20   | 51.75.82.166  | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Butch  | 1 | 
> 4809E3F9A73F5373734A4D23E7E7807A4743DD8A |
> |1 | 0 | 13:43:21   | 51.75.153.17  | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Beauty | 1 | 
> B66FBE3B2D9CE257AF75DEA760C69E379F7CDB80 |
> |1 | 0 | 13:43:22   | 51.68.170.74  | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Killer | 1 | 
> E4CB0C293588C3E5FA7DB94485FF2686E128267F |
> |1 | 0 | 13:43:23   | 51.68.185.141 | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Arrow  | 1 | 
> 707F51E232E0CDAF64EC446609E7112CD3AD11F8 |
> |1 | 0 | 13:43:24   | 54.37.207.82  | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Dazzle | 1 | 
> B80142DDCF8D6B72929541EFCC643ECCD99BEE36 |
> |1 | 0 | 13:50:41   | 145.239.1.97  | de   |   443 |  0 | 0.3.4.8 
>   | None  | Memo   | 1 | 
> 1C514FA1A4F8A464E1853B70AA5D2F16FF087AD2 |
> |1 | 0 | 13:50:42   | 51.38.107.122 | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Pitch  | 1 | 
> 91B026FA459AE0DA15673AB07A9C6DFF8B41782B |
> |1 | 0 | 13:50:43   | 51.68.186.59  | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Smasher| 1 | 
> 3B0EFDE689693CFDEC2305F7B99D5B2FA4A77D91 |
> |1 | 0 | 13:50:44   | 51.75.85.114  | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Landslide  | 1 | 
> C953A4C8DF0E233CB0D190C2A71B71F634AB4A14 |
> |1 | 0 | 13:50:45   | 51.68.182.30  | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Shade  | 1 | 
> EBE58DDCC51A9D23EE9DD39791695B608A1DFB29 |
> |1 | 0 | 13:50:46   | 54.37.207.37  | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Buster | 1 | 
> D10C82E275A2B0121CF4075C92687F0786A72892 |
> |1 | 0 | 13:50:47   | 54.37.200.157 | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Digger | 1 | 
> 6B29A78EEB42D318290DB60C6A2EDC714F1BAD42 |
> |1 | 0 | 13:50:48   | 54.37.207.84  | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Pipi   | 1 | 
> 150F7C9F4814C4918F4D2DEAA0C7A2255DC8C0E0 |
> |1 | 0 | 13:50:49   | 51.75.153.19  | fr   |   443 |  0 | 0.3.4.8 
>   | None  | Shrimp | 1 | 
> 51429A0F427A8DCB5B9DE64E35ECBBB76DAB0F7F |
> 
> https://nusenu.github.io/OrNetRadar/2018/10/24/a3
> 
> 
> -- 
> https://twitter.com/nusenu_
> https://mastodon.social/@nusenu
> 
> 
> 

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

[tor-relays] List purpose and moderation

[Colin Childs]

Hello tor-relays,

This message is to make everyone aware of the purpose of this list, and to
notify that off-topic posting will result in moderation. This is to
allow the list to continue being used as a relay operator support mechanism,
and to make sure the people on the list for this purpose are not driven away
by off-topic posts.

The stated purpose of this list is as follows:

Support and questions about running Tor relays (exit, non-exit, bridge)

Topics relating to this are encouraged and accepted on the list at any time.

However, this does not include:

Posts intended to troll / annoy members of the list
Acting as a support, publicity or communications channel for specific hosting 
providers
Posts regarding general tech news of the day

The tor-relays@ list is primarily a communication forum for current and
prospective relay operators to obtain support, plus share stories and 
experiences.

Relevant discussions about specific providers are also germane, although
any usage of this list for the purposes of publicity or as a
communications / support channel for providers is prohibited.

Thank you all for being part of the relay operator community!
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Exit Node shutdown

[Colin Childs]

Hi Sam,

Thank you for letting us know, and for being relay operators! 

> On Oct 12, 2018, at 7:41 AM, Tyler Durden  wrote:
> 
> Hi
> 
> Our two exit nodes "chulak" and "aurora" will be terminated by the end
> of this month. Both are listed in the Fallback Directory Mirror list and
> need to be removed.
> 
> Fingerprints:
> 379FB450010D17078B3766C2273303C358C3A442
> B0279A521375F3CB2AE210BDBFC645FDD2E1973A
> 
> 
> The shutdown is due to an internal reorganization.
> 
> 
> Greetings
> Sam Grüneisen - President FVDE
> ___
> 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] Reminder: Meeting in #tor-relays

[Colin Childs]

Hi everyone,

This is a reminder email that we will be holding a relay operator meeting on 
IRC this Tuesday, September 25th @ 19:00 UTC.

You can confirm your local date / time by visiting the following page, and 
selecting your timezone from the dropdown menu:

https://www.worldtimeserver.com/convert_time_in_UTC.aspx?y=2018=9=25=19=0

When: September 25th @ 19:00 UTC
Where: irc.oftc.net @ #tor-relays
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Mexico City operator meetup (October 2nd)

[Colin Childs]

Hello tor-relays,

At 6:30PM on October 2nd, the Tor Project will be hosting a relay operator 
meetup in Mexico City, at the Sheraton Maria Isabel[1][2].

Come along and meet other relay operators and hear the latest news from Tor — 
we’ll also have T-shirts and stickers to kit out your devices. If you don’t run 
a relay but would like to know more, there will be lots of people at the meetup 
happy to help you.

I also encourage you to read the complete blog post on the Tor Meeting Open 
Days linked below[1]. There are multiple other events happening around the 
meeting that relay operators may be interested in.

We would love to see you there, thank you all for being part of the relay 
operator community!

[1]: https://blog.torproject.org/hack-us-mexico-city-hackea-con-tor-en-mexico
[2]: Paseo de la Reforma 325, Cuauhtémoc, 06500 Ciudad de México, CDMX, Mexico
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Reminder: Meeting in #tor-relays

[Colin Childs]

Hi everyone,

As promised, this is a reminder email that we will be holding our first IRC 
relay operator meeting this week! 

When: September 11th @ 1:00AM UTC 
Where: irc.oftc.net  @ #tor-relays

You can confirm your local date / time by visiting the following page, and 
selecting your timezone from the dropdown menu:

https://www.worldtimeserver.com/convert_time_in_UTC.aspx?y=2018=9=11=1=0
 


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

Re: [tor-relays] Announcement: Relay operator meetings on IRC

[Colin Childs]

Hi Nusenu,

Yes, the current plan is to use MeetBot for the meetings. 

I will get a wiki page set up that the minutes / logs can be tracked on.

> On Aug 30, 2018, at 3:52 PM, nusenu  wrote:
> 
> Signed PGP part
>> Starting September 11th @ 1:00AM UTC, we will be piloting regular
>> relay operator meetings in #tor-relays on irc.oftc.net. 
> 
> 
> will you also use the meetbot like the other tor meetings do, so those that 
> can't join
> can read the log after the meeting?
> 
> 
> -- 
> https://twitter.com/nusenu_
> https://mastodon.social/@nusenu
> 
> 
> 

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

Re: [tor-relays] Announcement: Relay operator meetings on IRC

[Colin Childs]

Hi Rob,

The idea behind the two times is to allow people from different timezones / on 
different schedules to attend during their non-working hours. 

Overseas was the wrong choice of words, anyone is welcome to attend the meeting 
that works best for them (or both, if they choose to).

After the first two meetings, the plan is to evaluate if the given times worked 
or if they should be adjusted; or if only one meeting time is necessary.

> On Aug 30, 2018, at 5:51 PM, I  wrote:
> 
> -Original Message-
> From: co...@torproject.org
> Hello Tor relay operators!
> Starting September 11th @ 1:00AM UTC, we will be piloting regular relay 
> operator meetings in #tor-relays on irc.oftc.net . 
> For everyone overseas, we will be hosting a second meeting on September 25th 
> @ 19:00 UTC.
> 
> It is a good idea.
> What is the difference?  Why distinguish one meeting as being for overseas?  
> Presumably you mean outside USA?  The timing can't be the reason given the 
> earth is round.
> 
> Rob
> ___
> 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] Announcement: Relay operator meetings on IRC

[Colin Childs]

Hello Tor relay operators!

Starting September 11th @ 1:00AM UTC, we will be piloting regular relay 
operator meetings in #tor-relays on irc.oftc.net. These meetings will be an 
opportunity to introduce yourself to the operator community, make new contacts 
and provide updates to the group on the status of your relays. This will also 
be an opportunity to have questions answered by a group of dedicated relay 
operators, community members and Tor Project staff. 

For everyone overseas, we will be hosting a second meeting on September 25th @ 
19:00 UTC.

After these initial two meetings, we will evaluate if these dates / times need 
to be adjusted, as well as how frequently these meetings should be run. I will 
send a follow-up email at the end of September with the results of that 
evaluation. 

On the Monday of meeting weeks, I will send a reminder on this list with the 
channel, date and time.

I look forward to seeing you all there, and thank you for running relays! 

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

Re: [tor-relays] Yay, Complaints

[Colin Childs]

Hi Conrad,

Thank you for running exit relays and helping diversify the Tor network. I’m 
sorry to hear you’re experiencing this issue with Irdeto / your colocation 
facility, I understand how frustrating these situations can be. 

I’m going to reach out to you off list to discuss this issue further and offer 
some potential short-term / long-term solutions.

Thanks again, you should be receiving an email from me shortly. 

> On Aug 23, 2018, at 7:51 AM, Conrad Rockenhaus  wrote:
> 
> Signed PGP part
> So, new equipment gets plugged into a colo…. I’m a dude that was looking to 
> increase AS diversity on Tor and well, decided to add a new colo to the mix.
> 
> Two exit relays are brought online on properly SWIPed IP addresses. These 
> exit relays have only been online for about 24 hours.
> 
> An organization, known as Irdeto Intelligence, ignores the fact that the IP 
> addresses are SWIPed and sends abuse complaints to my upstream providers 
> asking them to straighten me out, because I’m a pox on society because people 
> are torrenting via Tor. They have sent over 40 emails in the last 12 hours.
> 
> Some dude-man, who calls himself a “Network Security Administrator” who asked 
> me to explain what Tor is……….because he’s a Network Security 
> Administrator……..has told me that due to the volume of complaints I need to 
> block the offending applications from their network.
> 
> I told him that I spoke with them prior to bringing this stuff online, 
> explained what Tor was, explained what a Tor exit was, explained that it will 
> generate complaints, explained the DCMA liability, explained the whole 
> thing…..and was told that they were okay with it.
> 
> I’m sorry for the bitching and moaning…it’s just another case of doing 
> everything right and now I’m quite worried that they’ll not only pull the 
> plug, that I’ll have to fight to get my Cisco UCS blade server back (and 
> other assorted equipment) which is totally not going to be cool.
> 
> Conrad
> 
> 

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

Re: [tor-relays] Become a Fallback Directory Mirror

[Colin Childs]

Hi Gunnar,

Either is alright! 

Thank you for getting in contact and offering your relay as a fallback 
directory mirror!

> On Jun 27, 2018, at 10:42 AM, Gunnar Wolf  wrote:
> 
> Colin Childs dijo [Tue, Jun 26, 2018 at 11:40:42AM -0500]:
>> Hello Tor Relay Operators,
>> 
>> Do you want your relay to be a Tor fallback directory mirror?
>> Will it have the same address and port for the next 2 years?
>> Just reply to this email with your relay's fingerprint.
> 
> You didn't specify whether the answer should go to the list or just to
> you. I hope I'm not needlessly spamming the world!
> 
> 4661DE96D3F8E923994B05218F23760C8D7935A4
> 
> Greetings,
> ___
> 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] Become a Fallback Directory Mirror

[Colin Childs]

Hello Tor Relay Operators,

Do you want your relay to be a Tor fallback directory mirror?
Will it have the same address and port for the next 2 years?
Just reply to this email with your relay's fingerprint.

If your relay is on the current list, you don't need to do anything.

If you're asking:

Q: What's a fallback directory mirror?

Fallback directory mirrors help Tor clients connect to the network.
For more details, see [1].

Q: Is my relay on the current list?

Search [2] and [3] for your relay fingerprint or IP address and port:

[2] is the current list of fallbacks in Tor.
[3] is used to create the next list of fallbacks.

Q: What do I need to do if my relay is on the list?

Keep the same IP address, keys, and ports.
Email tor-relays if the relay's details change.

Q: Can my relay be on the list next time?

We need fast relays that will be on the same IP address and port for 2
years. Reply to this email to get on the list, or to update the details
of your relay.

Once or twice a year, we run a script to choose about 150-200 relays
from the potential list [3] for the list in Tor [2].

Q: Why didn't my relay get on the list last time?

We check a relay's uptime, flags, and speed [4]. Sometimes, a relay might
be down when we check. That's ok, we will check it again next time.

It's good to have some new relays on the list every release. That helps
tor clients, because blocking a changing list is harder.

Q. I already have a relay in the fallback list, can I add another?

We will pick up to 7 relays per operator to be in the fallback list. Please 
send 
any relays that you would like considered for the fallback list.

Thanks for considering and/or being a fallback directory mirror!

[1]: https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors 

[2]: https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc 

[3]: 
https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist 

[4]: 
https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2017-05-16-0815-09cd78886.log
 
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] bridge installation help please

[Colin Childs]

Hi Rob,

The default log location on Debian changed some time ago to be your syslog 
instead of a file in /var/log/tor. 

If you would like to have tor log to a specific file, please add the following 
to your torrc and restart tor:

Log notice file /var/log/tor/log

I will get this page updated right away to reflect these changes, sorry for the 
confusion and thank you for running bridges. 

> On Jun 25, 2018, at 6:51 PM, I  wrote:
> 
> Keifer, thanks for the swift answer,
> 
> ! shift work
> 
> I followed 
> https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/obfs4proxy
>  
> 
> 
> on a vps with Debian 9
> the torrc reads
> 
> RunAsDaemon 1
> ORPort 9001
> BridgeRelay 1
> ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
> ExtORPort auto
> DataDirectory /var/lib/tor
> ContactInfo 
> Nickname 
> 
> from root this  
> 
> tail -F /var/log/tor/log
> 
> brought this
> 
> tail: cannot open '/var/log/tor/log' for reading: No such file or directory
> 
> Rob
> ___
> 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] Spam Emails Received From This Mailing List

[Colin Childs]

Just to fill in that information, the list I was referring to has 5 people on 
it (same 5 since it started) and by “closed”, I mean only the 5 of us were only 
ever able to register.

The archive has been open since the list began, and a few of us have been 
experiencing similar issues to what has been reported on this list. Not saying 
its whats happening here, but could be a useful note.

> On Jun 13, 2018, at 1:54 AM, grarpamp  wrote:
> 
> There's no point in overhead of repeatedly trolling and
> processing out stale archives when you can get valuable
> live bodies delivered instantly to your parsers for far less
> cost and work.
> 
> There are probably spam subs in Colin's list too,
> he didn't say which list, what exactly "closed" means,
> what subcount there is going back to when, etc.
> 
> Remote clouds and rspamd have learned them
> already since a while, faster, before they get shutdown.
> 
> Spooks are harder to kill than a little spam, work on those ;)
> ___
> 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] Spam Emails Received From This Mailing List

[Colin Childs]

Just to add some information:

I have started receiving these from a different (non-tor) mailing list, with 
addresses that look similar (and exact in the case of below)

This other list is closed, however the archives are open and we are assuming 
that the address harvesting is happening via the archive.

Its possible these spammers are operating similarly / could be the same ones.

> On Jun 11, 2018, at 5:49 PM, Mirimir  wrote:
> 
> On 06/11/2018 10:56 AM, Neel Chauhan wrote:
>> It seems that I am getting spam from a new email address:
>> camrynbentley870...@ao.ovsum.com
>> 
>> The pattern is that the emails are from *@*.ovsum.com addresses. Just
>> block this pattern as well, and report your emails to SpamCop.
> 
> Oh, and it seems that each user gets mail from a distinct sender. I get
> it from camrynbentley963...@np.ovsum.com. So they're keeping track. I
> wonder if they block replies from third parties.
> 
>> -Neel Chauhan
>> 
>> ===
>> 
>> https://www.neelc.org/
> 
> 
> 
> ___
> 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 Community Night / Relay operator night in Barcelona

[Colin Childs]

Hello tor-relays,

The Tor Project will be holding a community night / operator meet up 
after-hours at the 2018 Privacy Enhancing Technologies Symposium (PETS2018) in 
Barcelona! 

This will be happening on July 24th, at 6:30 PM in the PETS main room at Centre 
de Cultura Contemporània de Barcelona. At 8:30PM we will be moving to a near-by 
Belgian bar called "Belchica" at Carrer de Villarroel, 60, 08011 for food and 
drink. There will be Vegan options available.

This will be a great opportunity for the Tor relay operator community to meet 
and socialize. Within this event, there will be a dedicated relay operators 
meetup, which will begin at 7:00PM. We will discuss common issues operators 
face, potential solutions, as well as how we can all help to grow the relay 
operator community both locally and globally. We'll be on hand to answer 
questions and want to hear your feedback about the community, running relays, 
and what we can do to better support you.

Full details on the event can be found on our blog at 
https://blog.torproject.org/meetup-tor-community-night-pets 


I look forward to hearing from you / seeing as many of you there as possible!___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] FYI: Subpoena Received

[Colin Childs]

Hello everyone,

I just wanted to let people know that I have seen this thread and am looking 
into what may be going on. 

If anyone else received these but does not feel comfortable posting about them 
on the list, please do not hesitate to reach out to me directly with anything 
you feel comfortable sharing. I am not able to provide legal advice, but if 
this looks like a situation where legal advice will be required, I have some 
contacts who may be able to provide assistance.

Thank you for running exit relays.

> On Jun 8, 2018, at 5:43 AM, Matt Traudt  wrote:
> 
> 
> 
> On 06/08/2018 01:42 AM, "IPfail (Tor Admin)" wrote:
>> FYI, I received a subpoena from a US based court to produce information
>> about individual(s) who were using one of our exit nodes at a specific
>> date/time.  In the nearly 3 months that these exits have been in
>> operation, this is the first subpoena and only the second complaint
>> received.  For purposes of documenting the approximate ratio of
>> "complaints / traffic processed", these nodes have handled ~515TB and
>> are using the recommended reduced exit policy. 
>> https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy
>> 
> 
> I did too. Perhaps even from the same source...? Not sure if that can be
> shared so I just won't.
> 
> My exit isn't in the US, but I am.
> 
> Matt
> ___
> 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 Software Update Question

[Colin Childs]

Hi Keifer,

When doing Tor version upgrades (and not just config changes), there is no way 
to restart the process without losing uptime; as uptime records the amount of 
time that the Tor process has been running without interruption. 

When doing version upgrades, stopping your previous version of tor and starting 
the new version is required, this cannot be done without interrupting the 
uptime. That said, uptime is not a super important stat. It is more important 
that you keep your tor daemon / system up to date than go for high uptime 
numbers.

Thanks for running relays!

> On May 24, 2018, at 1:01 PM, Keifer Bly  wrote:
> 
> “killall tor” to stop the process then “tor” to start it again usually works, 
> but I wonder if there is a way to do this without loosing uptime as this 
> does? Thank you.
> 
> Sent from my iPhone
> 
>> On May 24, 2018, at 4:30 AM, Ralph Seichter  wrote:
>> 
>>> On 24.05.18 08:17, Valter Jansons wrote:
>>> 
>>> I have not worked on macOS services, but as I understand it, executing
>>> `sudo launchctl stop servicename && sudo launchctl stop servicename`
>>> should do the job for restarting the service [...]
>> 
>> That might not work as intended, depending on macOS version and service
>> configuration details. Both "stop" and "start" are legacy subcommands
>> aimed at on-demand services and older launchd implementations.
>> 
>>> Maybe just restarting the box is an easier method of restarting the
>>> Tor service.
>> 
>> Probably.
>> 
>> -Ralph
>> ___
>> 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] Relay advocate introduction

[Colin Childs]

Hi Torix,

Thank you for your ideas, I have made note of this and will review this list 
early next week.

I hope you all have a fantastic weekend!

> On May 17, 2018, at 4:44 PM, to...@protonmail.com wrote:
> 
> Dear Colin,
> 
> Perhaps your new role would cover this - I understand from the list that the 
> uneven distribution of the Tor network around the world is a concern.  My 
> first thought is that I should run a relay in India, which has a robust 
> internet, and speaks English.  However, I don't know whom to contact over 
> there to set something up.  I was wondering if it might be worth producing a 
> list of ISPs and urls in preferred geographically distributed countries.  
> 
> Maybe we have this resource already, but the closest page I've found is the 
> Good/Bad ISPs page:
> https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs
> but that includes mostly countries with  high percentages of tor relays, and 
> is mostly about ISP responses to exit nodes.
> 
> If I were a new person who wanted to run a relay, I would probably use the 
> cloud provider I know about or have connections with already.  If I had a 
> list of providers/urls in other countries, however, there would be a better 
> chance I would set it up somewhere else.
> 
> Just thinking..
> 
> --Torix
> 
> 
> ​Sent with ProtonMail Secure Email.​
> 
> ‐‐‐ Original Message ‐‐‐
> 
> On May 16, 2018 11:47 AM, Colin Childs <co...@torproject.org> wrote:
> 
>> Hello tor-relays!
>> 
>> My name is Colin Childs, I have been the support and translation coordinator 
>> at the Tor Project for a number of years. I am also a founding director of a 
>> TorServers partner named Coldhak here in Canada.
>> 
>> Recently, my role within the Tor Project has changed, and I am starting as 
>> the new relay advocate (as well as localization coordinator, until this 
>> responsibility can be reassigned). My job will be improving the health / 
>> happiness of the relay operator community, expanding the relay operator 
>> community, and helping improve the community bonds between operators.
>> 
>> A few of the things I will be working on are:
>> 
>> 1.  Open a #tor-relays IRC channel (this is now open, everyone should join!)
>> 2.  Reach out to realy operator groups / individuals to introduce myself and 
>> solicit feedback (beginning today)
>> 3.  Plan a relay operators meet-up at PETS in July (details to come in 
>> another email)
>> 4.  Form a team of trusted technical and legal volunteers able to help 
>> operators around the world.
>> 5.  Organizing a larger "relay operator summit" event
>> 6.  Working with operators to resolve some of the recent issues brought up 
>> on this list (DNS provider, DNSSEC, EOL releases, etc..)
>> 
>>While reaching out to operators is point 2 in that list, if you have 
>> suggestions or feedback that you'd like to send, please do not hesitate to 
>> reach out to me! I would love to hear from all of you with the things you 
>> would find most helpful from me / the Tor Project. While I cannot guarantee 
>> we can facilitate every request, we will do our best to help!
>> 
>>I look forward to working with all of you in the future, and I hope 
>> you're having a great week!
>> 
>> 
>> 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] New relay operator here

[Colin Childs]

Hi Privatesociety,

Thank you for setting up these relays and contributing to the Tor network! I 
look forward to working with you in the future.

In the #tor-relays IRC channel, there are a number of TorServers people, as 
well as people from partner organizations. There are also a number of us on 
this mailing list. Are you looking specifically to contribute to TorServers, or 
are you hoping to team up with a local partner organization / found your own 
partner org? 

If you’re unsure, I’d be happy to talk with you about options (as would other 
TS people, I’m sure). As Nusenu mentioned though, it would be helpful to know 
where you are based out of.

Thanks, talk soon!

> On May 17, 2018, at 2:08 PM, privatesociety Tor  
> wrote:
> 
> Hello tor relay community!
> I‘d like to introduce six new relays, which are operated by privatesociety, a 
> community of people, which fighting for privacy based in europe. The six 
> relays provide a capacity of around 300 mbit/s (total) and are hosted on 
> networks, which aren‘t much used - so better for the tor community. I hope we 
> are working great together. :)
> 
> Look at meetrics for more details: 
> https://metrics.torproject.org/rs.html#search/family:7AF3F4E88A5AE224DB775732A52731C8E54208A6
>  
> 
> 
> Anyway: We are maybe setting up an exit in the future, but for this we‘d like 
> to join forces with other exit operators like TORSERVERS.net to have better 
> connections in case of problems. Does anyone have contacts, which could be 
> helpful?
> ___
> 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 (was: Relay advocate introduction)

[Colin Childs]

Hello Nusenu,

Thank you for bringing this up and filing the ticket, this definitely sounds 
like something that should be brought back in some form. I’m going to look 
things over, review the history of Tor Weather and then make a plan for moving 
this forward. 

A monitoring service (like Tor Weather) has also been requested from a few 
other operators as well; so I think this is definitely something that will make 
the community happier as a whole.

> On May 17, 2018, at 2:44 PM, nusenu <nusenu-li...@riseup.net> wrote:
> 
> Colin Childs:
>> I would love to hear from all of you with the things you would find
>> most helpful from me / the Tor Project
> I believe the most useful tool for relay operators and
> the tor network as a whole would be to bring back Tor Weather.
> 
> I filed it as 
> https://trac.torproject.org/projects/tor/ticket/26124
> 
> 
> Full text bellow
> -
> TL;DR: I believe Tor Weather is the most efficient way to achieve and 
> maintain a healthy Tor network on the long run.
> 
> This is an item on the metrics team road map ("Q4 2018 or later") but maybe 
> the new relay advocate (Colin) can help with this?
> 
> Tor Weather has been discontinued on 2016-04-04,
> see Karsten's email for the reasoning behind it:
> https://lists.torproject.org/pipermail/tor-relays/2016-April/009009.html
> but as he says "Tor Weather is still a good idea, it just needs somebody to 
> implement it."
> 
> How Tor Weather looked like:
> https://web.archive.org/web/20141004055709/https://weather.torproject.org/subscribe/
> 
> 
> **Motivation**
> 
> If a relay disappears today, it is unlikely that anyone will notice or even 
> send an email to the operator unless it is a big one.
> 
> Relay operators and the entire tor network would benefit from a Tor Weather 
> service because it notifies relay operators when the state of their relays 
> changed (and more). This will increase the likelihood that relay operators 
> notice problems and actually mitigate the problem otherwise there is no "user 
> feedback" since tor can cope with disappearing relays quite well. 
> It also 
> * shows the relay operator that someone actually cares if their relays go 
> down or become outdated or have another problem
> * gives the operator relay best-practices information.
> 
> **Expected Effects**
> 
> If enough operators subscribe to such a service:
> * relays might become more long lived / the churn rate might decrease
> * the fraction of relays running outdated tor versions might decrease
> * the fraction of exits with broken DNS might decrease 
> 
> It also has the benefit of being able to contact relay operators 
> * completely automatically
> * even if they choose to not set a public ContactInfo string in their torrc 
> files.
> 
> **ideas for selectable notification types** 
> (sorted by importance)
> 
> Support subscribing via single relay FP or MyFamily groups (should not need 
> any subscription change if a relay gets added to the family).
> 
> [ ] Email me when my node is down
> How long before we send a notification? 
> [ ] email me when my relay is affected by a security vulnerability
> [ ] email me when my relay runs an end-of-life version of tor
> 
> [ ] email me when my relay runs an outdated tor version (note: this should 
> depend on the related onionoo bugs to avoid emailing alpha relay people)
> 
> [ ] email me when my exit relay fails to resolve hostnames (DNS failure)
> 
> [ ] email me when my relay looses the [ ] stable, [ ] guard, [ ] exit flag
> 
> [ ] email me when my MyFamily configuration is broken (meaning: non-mutual 
> config detected or relay with same contactInfo but no MyFamily)
> [ ] email me when you detect issues with my relay
> [ ] email me with suggestions for configuration improvements for my relay 
> (only once per improvement)
> 
> [ ] email me when my relay is on the top [ ] 20 [ ] 50 [ ] 100 relays list
> 
> [ ] email me with monthly/quarterly status information that includes 
> information like what my position in the overall relay list is (sorted by 
> CW), how much traffic my relay did during the last month and what fraction of 
> the months time your relay was included in consensus as running (this shows 
> information on how many % of the months' consensuses this relay has been 
> included and running)
> [ ] aggregate emails for all my relays into a single digest email
> [ ] email me about new relay requirements
> [ ] email me about tor relay operator events
> 
> * Write a specification describing the meaning of each checkbox
> 
> **Security and Privacy Implications**
> 
> The service stores email addresses of

[tor-relays] Relay advocate introduction

[Colin Childs]

Hello tor-relays!

My name is Colin Childs, I have been the support and translation coordinator at 
the Tor Project for a number of years. I am also a founding director of a 
TorServers partner named Coldhak here in Canada.

Recently, my role within the Tor Project has changed, and I am starting as the 
new relay advocate (as well as localization coordinator, until this 
responsibility can be reassigned). My job will be improving the health / 
happiness of the relay operator community, expanding the relay operator 
community, and helping improve the community bonds between operators.

A few of the things I will be working on are:

1. Open a #tor-relays IRC channel (this is now open, everyone should join!)
2. Reach out to realy operator groups / individuals to introduce myself and 
solicit feedback (beginning today)
3. Plan a relay operators meet-up at PETS in July (details to come in another 
email)
4. Form a team of trusted technical and legal volunteers able to help operators 
around the world.
5. Organizing a larger "relay operator summit" event
6. Working with operators to resolve some of the recent issues brought up on 
this list (DNS provider, DNSSEC, EOL releases, etc..)

While reaching out to operators is point 2 in that list, if you have 
suggestions or feedback that you'd like to send, please do not hesitate to 
reach out to me! I would love to hear from all of you with the things you would 
find most helpful from me / the Tor Project. While I cannot guarantee we can 
facilitate every request, we will do our best to help!

I look forward to working with all of you in the future, and I hope you're 
having a great week!


signature.asc
Description: Message signed with OpenPGP
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Tor program

[Colin Childs]

Hi Arisbe,

Here are some resources that may come in helpful, please feel free to reach out 
directly if you need any clarification or additional resources.

1. https://www.eff.org/pages/tor-and-https 
 this interactive graphic helps 
illustrate what Tor and HTTPS do.

2. https://support-staging.torproject.org/ 
 our new support portal, and will 
eventually also live at support.torproject.org 
, however it is currently already much nicer 
than the wiki. This has answers to frequently asked questions for a number of 
topics. If you find something missing or encounter an issue with the website, 
please let us know! 

3. https://www.youtube.com/watch?v=JWII85UlzKw 
 this is an animation about how 
the Tor Browser / Tor network can protect your privacy, we also have this in a 
number of languages available on the same channel 
https://www.youtube.com/user/TheTorProject/videos 
.

4. https://media.torproject.org/  this hosts a 
number of older presentations about Tor. These may help you in putting together 
your own slide deck, if that was a direction you were going in.

5. https://tb-manual.torproject.org/  This 
is our Tor Browser user manual. This also includes some information about 
censorship circumvention and accessing onion services. This is currently 
lagging behind the current Tor Browser release slightly as we wait for 
translations of some new strings. You will find the screenshots in the “alpha” 
folder have been updated to match the current Tor Browser release.

6. https://trac.torproject.org/projects/tor/wiki/TorRelayGuide 
 this is our new 
guide to running Tor relays. This may be overly technical for your talk, 
however it will give you a good idea of how the relays in the network are run. 

> On Mar 14, 2018, at 11:40 AM, Arisbe  wrote:
> 
> Hello People,
> 
> Does anyone have a graphic or verbal discussion about the Tor network that 
> they would share?  I want to give a talk at the public library about the 
> uses, advantage and how-to's of Tor.  I want to get my facts correct before I 
> commit to this task.
> 
> Thanks
> 
> ___
> 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