Re: [tor-relays] Become a Fallback Directory Mirror (deadline: July 23)
Nicenstein 7614EF326635DA810638E2F5D449D10AE2BB7158 Nicenstein3 FE3E691E5C804CBAB0C491F4365AA6B4267BF86E BurningMan 3CCF9573F59137E52787D9C322AC19D2BD090B70 AlanTuring 2BB85DC5BD3C6F0D81A4F2B5882176C6BF7ECF5A torturing 6F647831035CDB891B33103A073AEB9028122129 Nicenstein2 8E52CC35132AC6DF3781F539148781274D150919 Am 08.07.2020 um 19:36 schrieb gus: > Dear 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. > > Important: you have until July 23 2020 to reply to this message to get > in the fallback directory mirror list. > > If your relay is on the current fallback 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. > > cheers, > Gus > > [1] > https://gitlab.torproject.org/tpo/core/tor/-/wikis/NetworkTeam/FallbackDirectoryMirrors > [2] > https://gitweb.torproject.org/tor.git/tree/src/app/config/fallback_dirs.inc > [3] > https://gitweb.torproject.org/fallback-scripts.git/tree/fallback_offer_list > [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] Please help us find a working alternative to using MaxMind's GeoLite2 databases
Hi Karsten, I am the operator of relays "torturing" and "BurningMan". The right country for torturing is Netherlands and for BurningMan Finland. Cheers Am 07.07.2020 um 11:19 schrieb Karsten Loesing: > On 2020-02-12 16:05, Karsten Loesing wrote: >> Hi relay operators, >> >> as you might have heard, MaxMind has changed access and use of their >> GeoLite2 databases: >> >> https://blog.maxmind.com/2019/12/18/significant-changes-to-accessing-and-using-geolite2-databases/ >> >> This affects Onionoo and tor, and I'm trying to find a working >> alternative on the following ticket: >> >> https://trac.torproject.org/projects/tor/ticket/32978 >> >> Today I think I found a possible alternative by using data from another >> provider. But before I name it here, I'd first want to find out how >> accurate it is. >> >> I tried resolving relay IP addresses of relays that have been running in >> the past week and compared that to our existing lookups using MaxMind's >> October database. >> >> The result is that 7669 relays (93%) had the same country code and ASN. >> >> I put the remaining 7% on the following wiki page: >> >> https://trac.torproject.org/projects/tor/wiki/doc/MetricsGeoipComparison >> >> I'd like to hear from you which data source is right and which is wrong >> (or if both are wrong). >> >> If you'd like to help, please leave comments on the ticket or in the >> "Comment" column on that wiki page by February 19, 2020. >> >> Thanks for helping! > Hello again, > > I'm bumping this thread, because there's (finally) news on finding an > alternative to MaxMind: > > https://gitlab.torproject.org/tpo/metrics/trac/-/issues/32978 > > (Yes, you'll have to scroll down quite a bit to find the news, it's a > long ticket.) > > Can relay operators please take a look at that ticket and see if they > find their relay in the table with different country results? > > It would be neat to identify patterns there and possibly improve the > accuracy of the new database. > > Thanks for your help! > > All the best, > Karsten > > > ___ > 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] >23% Tor exit relay capacity found to be malicious - call for support for proposal to limit large scale malicious actors
Hi nusenu, this sounds quite useful and I would like to support it. I would be fine to do an email and physical address verifiation. Cheers Fabian Am 05.07.20 um 17:54 schrieb nusenu: > nick AT calyx dot com 0x2B791A2036D9D3AD.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] Authority Nodes
Hi Roger, what do we have to do to Opt-In as a Fallback Directory? Am 20.06.2020 um 13:00 schrieb niftybunny: ___ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
