[tor-relays] A general question for relay operators
Hello George and all, When I was learning to implement Tor I had difficulty wading through the web pages for information. Some pages were obsolete, some poorly maintained (think Tor flow or good/bad hosting companies). The Tor manual is just a huge list of Tor terminology with no aids to help find things. The Tor project site has no site map. I still occasionally have the same problems when I try to find something. I found this very discouraging as I tried to grow my first Tor node without a live person to help me. I can imagine how daunting this would be to someone also trying to learn linux. Hey, thanks so much for asking. I appreciate your interest. ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] A general question for relay operators
Arisbe, > > When I was learning to implement Tor I had difficulty wading through the > web pages for information It is odd for such well motivated people to leave such a mess unculled. The most useful help is outside the website. I hope a breath of fresh air is on the way. Rob ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] A general question for relay operators
Hi there, > what "things" do you wish you knew before you started running a relay? I wish I knew what the tor community and the tor network expects from us. For example, is it expected from us to keep the relay with 100% uptime? or would it be still fine to -say- have 70% uptime? or if it is not > 90% uptime, is it worthless to run it anyway? Or, more general, how much time and effort does it take to set it up and how much time and effort does it take to keep it running? What minimum knowledge do we need? What is the minimum requirement the relay must have to be it worth for the network? Also, I wish I knew what are the possible problems we may have to face and what to do with them (example, run out of bandwidth quota, cpu usage, possible intrusion and attack vectors to the server running the relay and how to prevent and mitigate them, ...) Sometimes I find those answers on tor's page/wiki or ask them on #tor-relay. Perhaps I didn't do enough research before setting up the relay ___ 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
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] Become a Fallback Directory Mirror
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
Re: [tor-relays] Become a Fallback Directory Mirror
Hi, you can include the following two relays for sure, as they are guaranteed to not change their ip / port: - 1E01B887F7FB61BEFC34FA8D9EA98E4268A8275F (rofltor02) - 41A3C16269C7B63DB6EB741DBDDB4E1F586B1592 (rofltor03) Currently rofltor03 has a traffic cap. I can change it to a long running and bandwidth (instead of traffic) capped relay tho, if that is wanted. The following relays can keep their ip / port, if you want to include them: - 8101421BEFCCF4C271D5483C5AABCAAD245BBB9D (rofltor01) - F741E5124CB12700DA946B78C9B2DD175D6CD2A1 (rofltor06) - 15BE17C99FACE24470D40AF782D6A9C692AB36D6 (rofltor07) - 90A5D1355C4B5840E950EB61E673863A6AE3ACA1 (rofltor09) - 3CB4193EF4E239FCEDC4DC43468E0B0D6B67ACC3 (rofltor10) Best regards, Matthias On 06/26/2018 06:40 PM, Colin Childs wrote: > 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 > ___ 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
> On 29 Jun 2018, at 07:39, Matthias Fetzer wrote: > > Currently rofltor03 has a traffic cap. I can change it to a long > running and bandwidth (instead of traffic) capped relay tho, if that > is wanted. How often does the relay reach its traffic cap? Becoming a fallback adds about 10 kilobytes per second of bandwidth. So it's not a good role for relays that have limited traffic or bandwidth. (We'd rather use those relays for user traffic.) T ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] A general question for relay operators
teor: > I think that is a part of the relay guide that we can improve: > Relays exist so that clients can use the network. > Consensus flags exist so that clients can use the network efficiently. > Bandwidth weights are assigned so that clients can use the network > efficiently. tracked as: https://trac.torproject.org/projects/tor/ticket/26562 -- https://twitter.com/nusenu_ https://mastodon.social/@nusenu signature.asc Description: OpenPGP digital signature ___ 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
> 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
Re: [tor-relays] A general question for relay operators
On 06/28/2018 01:19 AM, arisbe wrote: > Hello George and all, > > When I was learning to implement Tor I had difficulty wading through the > web pages for information. Some pages were obsolete, some poorly > maintained (think Tor flow or good/bad hosting companies). The Tor > manual is just a huge list of Tor terminology with no aids to help find > things. The Tor project site has no site map. I still occasionally > have the same problems when I try to find something. I found this very > discouraging as I tried to grow my first Tor node without a live person > to help me. I can imagine how daunting this would be to someone also > trying to learn linux. > > Hey, thanks so much for asking. I appreciate your interest. While the official Tor site arguably needs a thorough resign, designing a manifold manual for diverse interests and levels of ability AND threat models is no easy task. It's the classic security/ease of use conundrum! 0xDD79757F.asc Description: application/pgp-keys signature.asc Description: OpenPGP digital signature ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Re: [tor-relays] A general question for relay operators
> While the official Tor site arguably needs a thorough resign, designing > a manifold manual for diverse interests and levels of ability AND threat > models is no easy task. It's the classic security/ease of use conundrum! The part to do first and well is the advice for installing and setting-up a node. There should be less presumption and more of what to do when the results are not as stated. Robert ___ 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
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