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/FallbackDirec... [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_2...
787atxdotme 7AC93EC4B3725ABF7E09A903BC4A5C5C1E36517F
787atxdotmeonpi4 BD187CF1B44A84EC7DD1BC2AC9C4F7DE23D16619
William Pate willpate@pm.me 512-947-3311 inadequate.net
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, July 8, 2020 12:36 PM, gus gus@torproject.org wrote:
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/FallbackDirec... [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_2...
The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I run a bridge. Does that count?
-------- Original Message -------- On Jul 8, 2020, 1:36 PM, gus wrote:
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/FallbackDirec... [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_2... -- The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/ _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
94626BD21119568EB301D1E7677B272D27C20E3F
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, July 8, 2020 5:36 PM, gus gus@torproject.org wrote:
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/FallbackDirec... [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_2...
The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
5E56738E7F97AA81DEEF59AF28494293DFBFCCDF - Listed
29BBD80A1702C7FDEF6557C492F44E9EBAB2854A - Unlisted
-Dennis
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, July 8, 2020 5:36 PM, gus gus@torproject.org wrote:
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/FallbackDirec... [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_2...
The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/
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
576F242DC99996D31FFEF6DD5E083FD439ECF4C7
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/FallbackDirec... [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_2...
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
9B2BC7EFD661072AFADC533BE8DCF1C19D8C2DCC MIGHTYWANG
Viva la Wang!
On 08/07/20 18:36, gus wrote:
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/FallbackDirec... [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_2...
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
C14CE6C2145688B640EB6457F39C1C6E1DC684D4
Bill
On 08/07/20 18:36, gus wrote:
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.
-- William Denton :: Toronto, Canada --- Listening to Art: https://listeningtoart.org/ https://www.miskatonic.org/ --- GHG.EARTH: https://ghg.earth/ Caveat lector. --- STAPLR: https://staplr.org/
My relay Logforme (855BC2DABE24C861CD887DB9B2E950424B49FC34) is currently flagged as fallback dir. The relay runs on a dynamic ip address that will change rarely. I have over the years tried multiple times to get the relay excluded from the fallback dir list but it keeps popping back in there. Currently the ip address does not match what is listed in your linked document. Please remove the relay from the fallback dir list.
Aramis67 53C9F4954E7A7332BB0C610C5B8E04CA065AF29B
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, July 8, 2020 5:36 PM, gus gus@torproject.org wrote:
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/FallbackDirec... [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_2...
The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 08-07-2020 19:36, gus wrote:
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?
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.
As announced earlier on this list, my relay changed ISP, it is currently at line 892/893 of the fallback list at https://gitweb.torproject.org/fallback-scripts.git/tree/fallback_offer_list
* nick: ymkeo * fingerprint: 4E8CE6F5651E7342C1E7E5ED031E82078134FB0D * new IPv4: 185.238.129.9:9001 * new IPv6: [2a10:3781:116:1:ff:60ff:fe1e:4473]:9001
René
Hello Gus, My two exit relays in Moldova are offered as fallback directories. Like my other four exit/fallback relays, these are long-term investments that I hope will operate and grow for at least 5 more years. [D78D1B4489CF4FFB0FD74014BDF2D600D8EE5B05], [B06F093A3D4DFAD3E923F4F28A74901BD4F74EB1]. Best regards, stay safe,
Sent with ProtonMail Secure Email.
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Wednesday, July 8, 2020 10:36 AM, gus gus@torproject.org wrote:
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/FallbackDirec... [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_2...
The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
You can use my;8111FEB45EF2950EB8F84BFD8FF070AB07AEE9DD Cumprimentos;
D0F2882D84450F47C3FC922D5F6A262AB1395D6D
On 7/8/2020 1:36 PM, gus wrote:
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/FallbackDirec... [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_2...
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
08F4692B60862640F688B86826B66F30DEA7AB73
Le 8 juillet 2020 19:36:57 GMT+02:00, gus gus@torproject.org a écrit :
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/FallbackDirec... [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_2... -- The Tor Project Community Team Lead http://expyuzz4wqqyqhjn.onion/
CE47F0356D86CF0A1A2008D97623216D560FB0A8 52BFADA8BEAA01BA46C8F767F83C18E2FE50C1B9 8CAA470B905758742203E3EB45941719FCA9FEEC 1AE039EE0B11DB79E4B4B29CBA9F752864A0259E 03C3069E814E296EB18776EB61B1ECB754ED89FE 7600680249A22080ECC6173FBBF64D6FCF330A61 F9246DEF2B653807236DA134F2AEAB103D58ABFE 0C475BA4D3AA3C289B716F95954CAD616E50C4E5 AE6A8C18E7499B586CD36246AC4BCAFFBBF93AB2 8FA37B93397015B2BC5A525C908485260BE9F422 2CE96A8A1DA032664C90F574AFFBECE18A6E8DFC 9F5068310818ED7C70B0BC4087AB55CB12CB4377
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/FallbackDirec... [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_2...
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Cheers, Felix
D7082DB97E7F0481CBF4B88CA5F5683399E196A3 (https://metrics.torproject.org/rs.html#details/D7082DB97E7F0481CBF4B88CA5F56...)
(Thanks for having 39F096961ED2576975C866D450373A9913AFDC92 back on the proposal list)
-Sarah
On 2020-07-08 10:36, gus wrote:
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/FallbackDirec... [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_2... _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
# SERVER #1
# niftycastoroide MyFamily $9EEDBAD7EE351996DFC91578E882BEF4FE5EDBFA # niftyentry100 MyFamily $7ED3D8AFAC750F8CC0BDF8C87FE3BCBA2BBE2209 # niftyentry103 MyFamily $7226BE09B7A81000BBF7D959E360B2FE41CCC639 # niftyentry106 MyFamily $E6288334BC0F95345817811880DDEA184E63AE69 # niftyentry107 MyFamily $B2002D5C75A0FAD8F33962614718F35CB672CC57 # niftyentry108 MyFamily $28A4C64C34120E075701B0415D74906EC687F21F # niftyentry113 MyFamily $30E747B3058994CCCBEAF8B5B4791A9F1628AB7D # niftyentry115 MyFamily $5CCC3569C67B7F1BB733664D43DF4645F2A4B04D # niftyentry116 MyFamily $02758CD398E3F842EF82478078AAAE0273770DB2 # niftyentry117 MyFamily $BCDE75725B927738B6FD34EA2D78F4FA77B99848 # niftyexit1 MyFamily $EEB8F7554A54A96B51245AB47EB7B7DD99A98493 # niftyexit8 MyFamily $2E44E8EB8C7711C1157BD8025F07165CFF8FA2B6 # niftyexit MyFamily $E321D0118DAD44BBC74A5C26FE7CFDBAAF3DA077 # niftyhedgehog MyFamily $1084200B44021D308EA4253F256794671B1D099A # niftyhornedgopher MyFamily $6C64AE6D7EFDA52A463FB6ADCDAE2D2DDE0677C3 # niftyhousemouse MyFamily $E4B04C7D734B2294E8ECE057303E89B91EE88462 # niftyhutia MyFamily $644DECC5A1879C0FE23DE927DD7049F58BBDF349 # niftyjackrabbit MyFamily $CA37CD46799449D83B6B98B8C22C649906307888 # niftyjerboa MyFamily $8EE0534532EA31AA5172B1892F53B2F25C76EB02 # niftyjunipervole MyFamily $EDC4243F57F9B856B400398D5F6C354F8408EEA9 # niftylagurus MyFamily $1D89A810BDF84522B6036034F499A766EF294DB1 # niftyleithia MyFamily $F8E9C0C3A4B61E7599AA7A23D7ADE77E5BAB2663 # niftyllipika MyFamily $7DC52AE6667A30536BA2383CD102CFC24F20AD71 # niftymouse MyFamily $24E91955D969AEA1D80413C64FE106FAE7FD2EA9 # niftymuskrat MyFamily $7D921363817BE896B5462E90033DA937BEF7CE3F # niftyneochoerus MyFamily $2A231A5CA7AF91029B7475511D7D16DF85EC9221 # niftypedetes MyFamily $92A6085EABAADD928B6F8E871540A1A41CBC08BA # niftypedetidae MyFamily $71CFDEB4D9E00CCC3E31EC4E8A29E109BBC1FB36 # niftypika MyFamily $B771AA877687F88E6F1CA5354756DF6C8A7B6B24 # niftyporcupine MyFamily $7E281CD2C315C4F7A84BC7C8721C3BC974DDBFA3 # niftypygmyjerboa MyFamily $9B816A5B3EB20B8E4E9B9D1FBA299BD3F40F0320 # niftyquokka MyFamily $906DCB390F2BA987AE258D745E60BAAABAD31DE8 # niftyrabbitrat MyFamily $25526E61B8BC22B662E3D4A50504021CC3D9873D # niftyrat MyFamily $FDA70EC93DB01E3CB418CB6943B0C68464B18B4C # niftyredrockrat MyFamily $9B94A776DA2C0B974BF4E06A352133EDFE62036C # niftyredsquirrel MyFamily $97D2A26EA5C9972E66D23F4698E94DBDBA8F6C18 # niftysquirrel MyFamily $348B89013EDDD99E4755951D1EC284D9FED71226 # niftysteppemarmot MyFamily $48BE372CA2104D2422D49CD321060E7F697B52D9 # niftysugarglider MyFamily $47C42E2094EE482E7C9B586B10BABFB67557030B # niftytamiasaristus MyFamily $88AE3BC088396F1D3FCC4F2F588C0DC837599D20 # niftytamiasatsali MyFamily $957354D72042719C310A907FBFE42A3232C78757 # niftytreerat MyFamily $FAEC86A9A37152F0371D67917ABA398467DFBD9C # niftytucotuco MyFamily $619349D82424C601CAEB94161A4CF778993DAEE7 # niftyvolcanorabbit MyFamily $C08DE49658E5B3CFC6F2A952B453C4B608C9A16A # niftywoodlemming MyFamily $3F129FB71EB2B019B47403A5552EB2D40E5369F2 # niftywoodmouse MyFamily $14877C6384A9E793F422C8D1DDA447CACA4F7C4B
# SERVER #2
# niftyafricagiantrat MyFamily $56850752096EE63711F99B2FA5A812477561697D # niftyalloumyraion MyFamily $B4DD1F46C6E5B43D9654FF56BD32333D6586E536 # niftybankvole MyFamily $C00C28C2B1A7D8038517626CECA9BCB23B0A31D2 # niftybeaver MyFamily $6E94866ED8CA098BACDFD36D4E8E2B459B8A734E # niftyblythsvole MyFamily $E013CC98CCC1E6AFDCFC9681A53DC2DEFE5D4CCC # niftyboglemming MyFamily $0B3C8C2B2B1A1CA4429B9649F533BEB4D7470AEA # niftybunny MyFamily $B740BCECC4A9569232CDD45C0E1330BA0D030D33 # niftychionomy MyFamily $CD97DD0842A79184A7D057ECACEF7408C239C710 # niftychipmunk MyFamily $609E598FB6A00BCF7872906B602B705B64541C50 # niftycottonmouse MyFamily $28F4F392F8F19E3FBDE09616D9DB8143A1E2DDD3 # niftycottontail MyFamily $71AB4726D830FAE776D74AEF790CF04D8E0151B4 # niftydiatomys MyFamily $50B787A9FB21417BFD7B5067707DBF82D71DB11C # niftydormouse MyFamily $E6FAC9A7F33EE66F03C55C119770B2D45D3C576B # niftyeuropeanrabbit MyFamily $4031460683AE9E0512D3620C2758D98758AC6C93 # niftyfoxsquirrel MyFamily $9910C6DEEA9907EE7AEFCE0DA072F94F86EBFD48 # niftygerbil MyFamily $CDA2EA326E2272C57ACB26773D7252C211795B78 # niftyguard41 MyFamily $4AD0B40B0FC679CC300F398BCEBE9D000833F62C # niftyguard42 MyFamily $F8AEA2825629E4383599FD2A4BD5740CD1322CBC # niftyguard43 MyFamily $FB8796036069BB4787D639F92681ECC2FD7AEB22 # niftyguard44 MyFamily $5B9BB7A543C2C035A423A6B411780E50645782C0 # niftyguard46 MyFamily $AD1359B9D74D526FEF3F58AF41105C623A3A8C18 # niftyguard49 MyFamily $8839E8FBE28219B85392EEA5A4DBC41D315F4B83 # niftyguard51 MyFamily $8C9DF7FE2C6C8E253048D07EB1F3986841CF2407 # niftyguard52 MyFamily $6372CADE2B9A608E5114002A7A825AF0D11B449A # niftyguard54 MyFamily $4C07CB3365CF3E06A56FD2DC8ECA4E97A6521983 # niftyguard56 MyFamily $6CB7D0F355B60EF166439E96876BCDEBF8FD8E0F # niftyguard57 MyFamily $8054F105829438B029E7265BB1070F9258705112 # niftyguard59 MyFamily $BC38744FD82618B37EE6A5A61BBCCE8788D55E3D # niftyguard60 MyFamily $AF022F351A4B6F2514A09F9245F9FF5ACA729735 # niftyguard68 MyFamily $F1624D70C3AD373C849A5B2A8D07A20C73C0C7AD # niftyguard71 MyFamily $9634E9F53EB46828AE7E06839FEE595950286B1D # niftyguard74 MyFamily $A78E86015376B3F2507E2E6602FDFD278F2871B3 # niftyguard79 MyFamily $2FD03FFE27AF20DD6B1CBE5ABEFEF7B06693D557 # niftyguineapig MyFamily $EC1997D51892E4607C68E800549A1E7E4694005A # niftyhare MyFamily $6781471814DF164C2A6F17CD1F2584923FDE2101 # niftyhazelmouse MyFamily $0FB2EDAB99D10A2B708370E625323C76EB895FA2 # niftyleastchipmunk MyFamily $34F5D33DD46D7FBD380B11567132A18773BC4F57 # niftysnowshoehare MyFamily $A3901DDB7799A11E9BAB90BD1DDA734DBA196337 # niftyspinymouse MyFamily $986E29FB17C8C7A1FEAFF203F012D5930BA079DB # niftytelicomys MyFamily $D27208881BBDB5EA56EFD1D1799187519591E325 # niftywabbit11 MyFamily $520C85ABE6E731CECC28B1055854053FAA28061B # niftywabbit12 MyFamily $A078B48882C22F1E7A527E219DCD745086F2BB5C # niftywabbit13 MyFamily $2AAEB8B74A2CC33E650402F427A9CA18D89135D9 # niftywabbit14 MyFamily $24352D30196BEFE5BB29A50923F79A2804527611 # niftywabbit15 MyFamily $4AD9C116A1942D58A714433CA24F087F18036A7E # niftywabbit16 MyFamily $9664A7EFB405F555F3C0079FA7618B2EE6CE6D2A # niftywabbit17 MyFamily $62942921319A5BEC6FF3474B84DA0908B60E5505 # niftywabbit18 MyFamily $CBC05B0C4B789ED162F74733C0FFC2EB6AB4D494 # niftywabbit19 MyFamily $C74469EC04787CC458FB1DCDF456C5092CF08B19 # niftywabbit20 MyFamily $BFB4AF1E77A834341280041E9B608C4074F55132 # niftywoodlandvole MyFamily $283312BB249FCB6633A7C7E1E8241461000E6004
# SERVER #3
# niftyentry62 MyFamily $44BE8503A486DAA41208F18957D3E757806625C9 # niftyentry63 MyFamily $A03ABD9D586255C8C33B3A2730E64848CAB11ED3 # niftyentry64 MyFamily $D286ED33FCB28385BAD9DA3D6B12A604C0834313 # niftyentry67 MyFamily $EE859849E8D8EF083EEF2025555396A6C3552A8E # niftyentry68 MyFamily $B3407384A86D866D6DC31A37533C8703DBD64965 # niftyentrynice MyFamily $7B7C7F31205D7AEB5DFFEDA08E00282A78CD76E0 # niftyentry70 MyFamily $ED6AF8CE8CF4126A6F33572376B6D8977FED2DD9 # niftyentry71 MyFamily $E330A88754840629644527394FD43001D5B89C7A # niftyentry74 MyFamily $8FF2896A94BCAA5F0A7C5A56AD6586492CD448AF # niftyentry60 MyFamily $621EA822CEAC095845A0CFFFA503D2993AB10FF3 # niftyentry77 MyFamily $01FDC8E92D3280847D856DA1F9BFC2B4CD2C2EE8 # niftyentry78 MyFamily $380F79145FF9C2332CBF41313062C99DBA9B0E50 # niftyentry79 MyFamily $71730F1BEB5372C9A6FF36704FF1A6A48AEE7813 # niftyentry80 MyFamily $8BE58BA7A28DC6B4F211CE8EE86783B85133488D # niftyentry83 MyFamily $562C61C7F885741D599DB7A1235791D928BEADFD # niftyentry84 MyFamily $C10DAA8C8A3025FE92E1C337E030950536DE8DE6 # niftyentry85 MyFamily $C6E184C0983C68B7E8BFC6215E7289E09E97AA0E # niftyentry88 MyFamily $E2B9BA96723C59E65AE07E82B74C7A31AF874225 # niftyentry89 MyFamily $38012983E82E0C0824CBD62E4350607F8CF9497A # niftyentry92 MyFamily $95B9052EECDB4B833F130ABD564E720643BA7952 # niftyentry94 MyFamily $CAD1476D23CD380F6F0E980FBE5F5EF4A1FDE915 # niftyentry95 MyFamily $863FDDA3CA537CE03646B3AEBD3FD1CC6B077FBE # niftyentry96 MyFamily $FD481A525D86BF85FF616DC47C83CDF886D354DF # niftyentry97 MyFamily $66B861BA080167315AE3D04FB12F109658F50A72 # niftyentry98 MyFamily $4942750656EAD6A119128C3D28FD653D6BC148A2 # niftyentry99 MyFamily $8CA736F332937E4FA0F5F48488B823F31883123C # niftyguard02 MyFamily $7F7BE7926AF718D6A3DED24D694D94C1D5FACF28 # niftyguard07 MyFamily $C8F6F6C1834454F1E927A4A05E8E54EB623D4B73 # niftyguard08 MyFamily $D52BA077CACA90197935C9BFFC3138860613ECCE # niftyguard09 MyFamily $31F373571AA6ECB4D73266E114D58B0AF7227369 # niftyguard11 MyFamily $FDBF608F9A2ECD0C600CAF96398A7D5B08D46CA9 # niftyguard15 MyFamily $05F5BB75DA007361CE03770393033D4D52836D8A # niftyguard19 MyFamily $0A4ED4C74020740A904F3A9936030B7A4C6170BB # niftyguard MyFamily $456F6E4998EB17B975DB5A19273607868E5F8AFA # niftyguard21 MyFamily $7404DC4E6B17D5B751BF343E509F6D4B940FC104 # niftyguard26 MyFamily $583CEFCFF76B3189D3A37C81A49D1619D04DCB34 # niftyguard34 MyFamily $E9DEDC208BC55A8E2901CC50E537A975EE5CF1B3 # niftyguard36 MyFamily $1B9235656503E80E913E9C9A139AD89D36E2DFFD # niftyguard41 MyFamily $51AE0E9E7CFAE8C07A66C705A7A55743C20B171C # niftyguard42 MyFamily $7F138EE16BC1F21214E902FB6B8E6C4E6CE1CF28 # niftywabbit MyFamily $30DBF7A773F4EE3BF6D1B7407DAECF40220AC8CD # niftywabbit MyFamily $A14F90953AE9462CF3A862C4CA95F73BF94A6F8B # niftywabbit11 MyFamily $D28A5F1BBB82CD59807FAF9A1260422092775DA2 # niftywabbit12 MyFamily $902E21BC05A7B1EC8CE85D78C47C3D8EAD5EFE6F # niftywabbit13 MyFamily $1B605B2751279B152CA098ED76B1EBCC9ADCA239 # niftywabbit11 MyFamily $FC23AF735E7828834688AC8E3ACA2661916495C6 # niftywabbit15 MyFamily $6D45BF799AB989BE7D8F045A489CCDDF38D4D20A # niftywabbit16 MyFamily $FF1ED9A17F6081DEB4607FDAF43FADF16B94A955 # niftywabbit17 MyFamily $B36006D88E2CCEF2E1EF0826C7F1B0EDC8DE6C06 # niftywabbit18 MyFamily $50A0CFB654D39F420F52D362B1DF50A12B33D5A0 # niftywabbit19 MyFamily $39F17EC1BD41E652D1B80484D268E3933476FF42 # niftywabbit2 MyFamily $2F64EA527C4AA6F99E261318DD1FF127828E2525 # niftywabbit20 MyFamily $470BC5C6A8BD1D9FDBB55689FB3030310181EAE2 # niftywabbit3 MyFamily $C47E8F025645C621BE8BF8B5F6C8564A41259F7B # niftywabbit4 MyFamily $53CBD4285918F168B92D05CAA9BC0CF499DF72C7 # niftywabbit5 MyFamily $DFAA86AD46BEA875D5018CC1CECD77C9F979FB0E # niftywabbit6 MyFamily $7C7FFB1C48B7E0C5C9B3D11FEC2F8500F464786A # niftywabbit MyFamily $10644CF3D7F555F10FE28EB1D520111F56FE7180 # niftywabbit8 MyFamily $FDFD675D05216549EB7DA545E32ECFCEEAE805F2 # niftywabbit9 MyFamily $50D1473A213DB343E97664C71C09D28EC2692CB3
On 17. Jul 2020, at 06:54, Sarah Harvey s@shh.sh wrote:
D7082DB97E7F0481CBF4B88CA5F5683399E196A3 (https://metrics.torproject.org/rs.html#details/D7082DB97E7F0481CBF4B88CA5F56... https://metrics.torproject.org/rs.html#details/D7082DB97E7F0481CBF4B88CA5F5683399E196A3)
(Thanks for having 39F096961ED2576975C866D450373A9913AFDC92 back on the proposal list)
-Sarah
On 2020-07-08 10:36, gus wrote:
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/FallbackDirec... [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_2... _______________________________________________ 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 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 https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Nos oignons' relays:
F47B 13BF CE4E F48C DEF6 C4D7 C7A9 9208 EBB9 72B5 8E6E DA78 D8E3 ABA8 8D87 7C3E 37D6 D4F0 938C 7B9F 90FD 830C 357A 5109 AB3C 5052 8771 3F1A C811 174C 578E 007E 5E45 35FB FEF7 758D 8587 B07B 4C8C 5D06 9BA8 4E8C 9008 3676 F86C 7427 C8D1 0592 5F13 716C C656 B41A EFB4 0A14 1967 EBF4 9D6E 6960 3C9B 4A11 EFAE 4472 8264 9822 2444 5E96 214C 15F9 075D EE1D
Clients can and will fetch directory information over the ORPort, right?
If so, then count me in:
https://metrics.torproject.org/rs.html#details/47E1157F7DA6DF80EC00D745D73AC...
2020-07-19 19:45 GMT, jvoisin julien.voisin@dustri.org:
Nos oignons' relays:
F47B 13BF CE4E F48C DEF6 C4D7 C7A9 9208 EBB9 72B5 8E6E DA78 D8E3 ABA8 8D87 7C3E 37D6 D4F0 938C 7B9F 90FD 830C 357A 5109 AB3C 5052 8771 3F1A C811 174C 578E 007E 5E45 35FB FEF7 758D 8587 B07B 4C8C 5D06 9BA8 4E8C 9008 3676 F86C 7427 C8D1 0592 5F13 716C C656 B41A EFB4 0A14 1967 EBF4 9D6E 6960 3C9B 4A11 EFAE 4472 8264 9822 2444 5E96 214C 15F9 075D EE1D _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Am Mi., 8. Juli 2020 um 19:37 Uhr schrieb gus gus@torproject.org:
Will it have the same address and port for the next 2 years?
Search [2] and [3] for your relay fingerprint or IP address and port.
Keep the same IP address, keys, and ports.
We need fast relays that will be on the same IP address and port for 2 years.
Port or Ports? If Port, which one?
I guess you are talking about the ORPort because i changed the DirPort of one of my current fallbacks yesterday and it still has the Fallback flag.
I would like to opt-in:
F8AA8D8CCBA0C5F2836DE6315CDFA6E4A31A0890 B93503D458D9FE97DE5C12D211082871D08F1284 7AAF5597B18D82CC90CA95FB7976A1CEA4A32E06 57C6DF5B93E54EB9C8DB90029D9E9A1111BD34D2
Thanks!
On 08 Jul (13:36:57), gus wrote:
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?
Greetings operators!
First off, we got 225 relays to volunteer for this round which is incredible so thank you so much to all of you!
The new list has been generated and can be found here:
https://gitlab.torproject.org/tpo/core/fallback-scripts/-/blob/master/fallba... Diff: https://gitlab.torproject.org/tpo/core/fallback-scripts/-/commit/0aa75bf9eaa... In tor binary: https://gitlab.torproject.org/tpo/core/tor/-/blob/master/src/app/config/fall...
This new list will take effect once we release these new stable and alpha versions:
- 0.3.5.12 - 0.4.1.10 - 0.4.2.9 - 0.4.3.7 - 0.4.4.3-alpha
There are many requirements to fulfill to be in this list so even if you volunteered your relay, you might not end up in the list. Don't worry, the more numbers we have the better we can insure stability thus you already helped greatly!
We'll be tracking any changes to this list here:
https://gitlab.torproject.org/tpo/core/fallback-scripts/-/issues/40001
Please let us know if you need to change/remove your relay from the current list. Mistake could have been made thus a validation would be welcome!
We'll make a general call around May 2021 to rebuild the list with new volunteers unless we go below 25% unreachable relays.
Thanks a lot everyone! David
On 24 Jul (13:30:31), David Goulet wrote:
The new list has been generated and can be found here:
Apology, clarification needs to be made:
https://gitlab.torproject.org/tpo/core/fallback-scripts/-/blob/master/fallba... Diff: https://gitlab.torproject.org/tpo/core/fallback-scripts/-/commit/0aa75bf9eaa...
The offered list ^ that is all the relays that offered to help since the dawn of time.
In tor binary: https://gitlab.torproject.org/tpo/core/tor/-/blob/master/src/app/config/fall...
The generated list that ended up in the binary. Thus this list needs to be reviewed for accuracy if you ended up in :).
Sorry for the possible confusion!
David
Am Fr., 24. Juli 2020 um 19:36 Uhr schrieb David Goulet < dgoulet@torproject.org>:
In tor binary:
https://gitlab.torproject.org/tpo/core/tor/-/blob/master/src/app/config/fall...
The generated list that ended up in the binary. Thus this list needs to be reviewed for accuracy if you ended up in :).
Something seems wrong with this list.
This fingerprint of one of my relays never got opted-in by me. FF9FC6D130FA26AE3AE8B23688691DC419F0F22E
When i remember correctly then the old fingerprint of the relay on this IP was a fallback but i did a clean install with Debian 10 and didnt kept the keys because i dont wanted it to be a fallback anymore.
So why is it on the list now?
And is it normal that this list does not list any of my relays that are currently fallbacks and none of the relays that i opted-in?
On Fri, Jul 24, 2020 at 1:36 PM David Goulet dgoulet@torproject.org wrote:
On 24 Jul (13:30:31), David Goulet wrote:
The new list has been generated and can be found here:
Apology, clarification needs to be made:
https://gitlab.torproject.org/tpo/core/fallback-scripts/-/blob/master/fallba... Diff: https://gitlab.torproject.org/tpo/core/fallback-scripts/-/commit/0aa75bf9eaa...
The offered list ^ that is all the relays that offered to help since the dawn of time.
In tor binary: https://gitlab.torproject.org/tpo/core/tor/-/blob/master/src/app/config/fall...
The generated list that ended up in the binary. Thus this list needs to be reviewed for accuracy if you ended up in :).
Sorry for the possible confusion!
David
Hi, everybody! David is on vacation now, and will be back in mid-August. He'll be able to make any changes to the generated list then. Between now and then, the recently generated list might appear in a couple of alphas, but not in any stable releases.
Please let me know if there is a super-important change that needs to happen to the list before it goes in any alphas. Otherwise, please don't worry if you don't get a reply until David is back.
best wishes to all,
Am Mo., 27. Juli 2020 um 02:31 Uhr schrieb Nick Mathewson < nickm@torproject.org>:
On Fri, Jul 24, 2020 at 1:36 PM David Goulet dgoulet@torproject.org wrote:
On 24 Jul (13:30:31), David Goulet wrote:
The new list has been generated and can be found here:
Apology, clarification needs to be made:
https://gitlab.torproject.org/tpo/core/fallback-scripts/-/blob/master/fallba...
Diff:
https://gitlab.torproject.org/tpo/core/fallback-scripts/-/commit/0aa75bf9eaa...
The offered list ^ that is all the relays that offered to help since the dawn of time.
In tor binary:
https://gitlab.torproject.org/tpo/core/tor/-/blob/master/src/app/config/fall...
The generated list that ended up in the binary. Thus this list needs to
be
reviewed for accuracy if you ended up in :).
Sorry for the possible confusion!
David
Hi, everybody! David is on vacation now, and will be back in mid-August. He'll be able to make any changes to the generated list then. Between now and then, the recently generated list might appear in a couple of alphas, but not in any stable releases.
Please let me know if there is a super-important change that needs to happen to the list before it goes in any alphas. Otherwise, please don't worry if you don't get a reply until David is back.
best wishes to all,
Nick
Great according to the Fallback flag in metrics the only relay i don't want to be a fallback anymore is a fallback now and all my other relays that were fallbacks previously are no fallbacks anymore and the list now appears in a stable release.
The relay of the other operator who asked multiple times to get removed from the fallback list is a fallback as well.
What now? How far away do i need to throw the keys to not get it listed again?
On 9/17/20 11:51 AM, Toralf Förster wrote:
On 9/16/20 1:05 AM, Michael Gerstacker wrote:
the only relay i don't want to be a fallback anymore is a fallback now
Maybe OT but I'm just curious about the reason to want a relay being not a fallback.
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
If the operator intends on changing addresses or disabling the relay it probably shouldn't be added to the fallback set.
Am Do., 17. Sept. 2020 um 20:51 Uhr schrieb Toralf Förster < toralf.foerster@gmx.de>:
On 9/16/20 1:05 AM, Michael Gerstacker wrote:
the only relay i don't want to be a fallback anymore is a fallback now
Maybe OT but I'm just curious about the reason to want a relay being not a fallback.
First reasons why i don't want that this one relay of mine is a fallback:
1. It is heavily used and can barely keep up with the traffic. Even if fallback traffic is low i have plenty of other relays that are bored right now.
2. I plan to switch it to an exit maybe and i don't think exits should be fallbacks. They draw attention, they are blacklisted, they are hated and depending in which country they are maybe even watched by some higher authority. So i think users connecting to fallbacks that are exits should be avoided. Again i have plenty of other relays that are no exits and where i don't plan to make them exits so i think these ones are better for being a fallback.
Not related to that one relay but other reasons why i don't want that some relays of mine are fallbacks:
3. I have relays in countries where the government doesn't really like Tor. If my provider would be forced to shut them down (or just shut them down because he doesn't like Tor) then if the relay is not a fallback soon after it went down no users will try to connect to it anymore and after a week or two it is gone from metrics.
If it is a fallback then for weeks, months maybe even years users with old Tor versions will try to connect to these addresses because Tor expects a fallback there.
Maybe having fallbacks in these countries is even more important but again as long as i have relays that are really bored and as long as i can only opt-in a limited amount of relays i prefer to choose ones that are not located in these countries and maybe it even helps my provider with not getting any future problems with their regime.
4. I didn't checked it but some provider have a crazy TOS and i would not be surprised if some of them write there that it is not allowed to hardcode the IP you get from them into anything to prevent them from reason 3 where old versions of a software are abusing their IPs when it is already long gone. But exactly that is what you do with opting-in as a fallback.
Maybe there are more reasons but these are the ones i have in my head right now.
It is not the end of the world that this one relay is a fallback now. But it is surprising because that particular fingerprint never got opted-in by me so i think something went wrong somewhere.
The new list has been generated and can be found here:
https://gitlab.torproject.org/tpo/core/fallback-scripts/-/blob/master/fallba...
I don't understand this section: # These fallbacks opted-in in previous releases, then changed their details,# and so we blacklisted them. Now we want to whitelist changes.# Assume details update is permanent85.230.184.93:9030 orport=443 id=855BC2DABE24C861CD887DB9B2E950424B49FC34 # Logforme Logforme is my relay. I've repeatedly asked for it to be blacklisted. Does "Now we want to whitelist changes" mean you want to whitelist the relay? Please don't. Btw the ip listed is not the current one.
tor-relays@lists.torproject.org
-
Anonforpeace -
BackplaneDNS -
David Goulet -
Felix -
gnu1170＠tuta.io -
gus -
John Csuti -
Jordan -
jvoisin -
Logforme -
marsbanks -
Michael Gerstacker -
Mighty Wang -
Nick Mathewson -
niftybunny -
Nuno Rego -
potlatch -
René Ladan -
Sarah Harvey -
Simon Fernandez -
Tor-abuse -
Toralf Förster -
torix＠protonmail.com -
William Denton -
William Kane -
William Pate