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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please: * make sure it has enough available file descriptors, and * set MaxMemInQueues to the amount of RAM you have available per tor instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
[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_2... [5]: https://lists.torproject.org/pipermail/tor-relays/2017-December/013881.html
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------
Tim,
0077BCBA7244DB3E6A5ED2746E86170066684887 041646640AB306EA74B001966E86169B04CC88D2 155D6F57425F16C0624D77777641E4EB1B47C6F0 1AE949967F82BBE7534A3D6BA77A7EBE1CED4369 1DB25DF59DAA01B5BE3D3CEB8AFED115940EBE8B 1E5136DDC52FAE1219208F0A6BADB0BA62587EE6 2ED4D25766973713EB8C56A290BF07E06B85BF12 3687FEC7E73F61AC66F7AE251E7DEE6BBD8C0252 36D68478366CB8627866757EBCE7FB3C17FC1CB8 3CA0D15567024D2E0B557DC0CF3E962B37999A79 40E7D6CE5085E4CDDA31D51A29D1457EB53F12AD 43209F6D50C657A56FE79AF01CA69F9EF19BD338 54A4820B46E65509BF3E2B892E66930A41759DE9 5649CB2158DA94FB747415F26628BEC07FA57616 5F4CD12099AF20FAF9ADFDCEC65316A376D0201C 60D3667F56AEC5C69CF7E8F557DB21DDF6C36060 66E19E8C4773086F669A1E06A3F8C23B6C079129 764BF8A03868F84C8F323C1A676AA254B80DC3BF 7A3DD280EA4CD4DD16EF8C67B93D9BDE184D1A81 7E6E9A6FDDB8DC7C92F0CFCC3CBE76C29F061799 7FA8E7E44F1392A4E40FFC3B69DB3B00091B7FD3 8B80169BEF71450FC4069A190853523B7AEA45E1 9314BD9503B9014261A65C221D77E57389DBCCC1 9C1E7D92115D431385B8CAEA6A7C15FB89CE236B 9D21F034C3BFF4E7737D08CF775DC1745706801F 9E2D7C6981269404AA1970B53891701A20424EF8 9F2856F6D2B89AD4EF6D5723FAB167DB5A53519A A0DB820FEC87C0405F7BF05DEE5E4ADED2BB9904 A4A393FEF48640961AACE92D041934B55348CEF9 B028707969D8ED84E6DEA597A884F78AAD471971 B0CD9F9B5B60651ADC5919C0F1EAA87DBA1D9249 B2197C23A4FF5D1C49EE45BA7688BA8BCCD89A0B B6320E44A230302C7BF9319E67597A9B87882241 B7047FBDE9C53C39011CA84E5CB2A8E3543066D0 C78AFFEEE320EA0F860961763E613FD2FAC855F5 CB7C0D841FE376EF43F7845FF201B0290C0A239E CC14C97F1D23EE97766828FC8ED8582E21E11665 CC4A3AE960E3617F49BF9887B79186C14CBA6813 D25210CE07C49F2A4F2BC7A506EB0F5EA7F5E2C2 D33292FEDE24DD40F2385283E55C87F85C0943B6 D6FF2697CEA5C0C7DA84797C2E71163814FC2466 DF20497E487A979995D851A5BCEC313DF7E5BC51 E480D577F58E782A5BC4FA6F49A6650E9389302F EABC2DD0D47B5DB11F2D37EB3C60C2A4D91C10F2 EC15DB62D9101481F364DE52EB8313C838BDDC29 F21DE9C7DE31601D9716781E17E24380887883D1 F7447E99EB5CBD4D5EB913EE0E35AC642B5C1EF3 FDD700C791CC6BB0AC1C2099A82CBC367AD4B764 FE00A3A835680E67FBBC895A724E2657BB253E97
John L. Ricketts, Ph.D. Quintex Alliance Consulting (325) 262-3488 Cell/Signal
-----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of teor Sent: Wednesday, December 20, 2017 5:51 PM To: tor-relays@lists.torproject.org Subject: [tor-relays] Become a Fallback Directory Mirror
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please: * make sure it has enough available file descriptors, and * set MaxMemInQueues to the amount of RAM you have available per tor instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
[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_2... [5]: https://lists.torproject.org/pipermail/tor-relays/2017-December/013881.html
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------
Tim,
Oh.. and
C5A53BCC174EF8FD0DCB223E4AA929FA557DEDB2
John L. Ricketts, Ph.D. Quintex Alliance Consulting (325) 262-3488 Cell/Signal
-----Original Message----- From: tor-relays [mailto:tor-relays-bounces@lists.torproject.org] On Behalf Of teor Sent: Wednesday, December 20, 2017 5:51 PM To: tor-relays@lists.torproject.org Subject: [tor-relays] Become a Fallback Directory Mirror
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please: * make sure it has enough available file descriptors, and * set MaxMemInQueues to the amount of RAM you have available per tor instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
[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_2... [5]: https://lists.torproject.org/pipermail/tor-relays/2017-December/013881.html
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n ------------------------------------------------------------------------
Hi Tim, Be my guest 775B0FAFDE71AADC23FFC8782B7BEB1D5A92733E EFEACD781604EB80FBC025EDEDEA2D523AEAAA2F 484A10BA2B8D48A5F0216674C8DD50EF27BC32F3 1938EBACBB1A7BFA888D9623C90061130E63BB3F Best Regards Anders Burmeister
Sent with [ProtonMail](https://protonmail.com) Secure Email.
-------- Original Message -------- Subject: [tor-relays] Become a Fallback Directory Mirror Local Time: 21 December 2017 12:50 AM UTC Time: 20 December 2017 23:50 From: teor2345@gmail.com To: tor-relays@lists.torproject.org
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please:
- make sure it has enough available file descriptors, and
- set MaxMemInQueues to the amount of RAM you have available per tor
instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
D8972986BE19E0287770DF51C47C630A53DC6E97
Thanks -Aneesh
On Fri, Dec 22, 2017 at 4:51 AM, Franklin Bynum franklin@bynumlaw.net wrote:
78E2BE744A53631B4AAB781468E94C52AB73968B _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 22 Dec 2017, at 16:37, Aneesh Dogra lionaneesh@gmail.com wrote:
D8972986BE19E0287770DF51C47C630A53DC6E97
Thanks -Aneesh
Hi Aneesh,
Your relay needs a DirPort to be a fallback directory mirror. (This is an old requirement, we hope to fix it at some point.)
Your DirPort should be on 9030 by default. Or you can configure a DirPort on PORT_NUMBER using:
DirPort PORT_NUMBER
Let us know when you've configured a DirPort, and we'll put your relay on the list.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
On Fri, Dec 22, 2017 at 3:51 PM, teor teor2345@gmail.com wrote:
On 22 Dec 2017, at 16:37, Aneesh Dogra lionaneesh@gmail.com wrote:
D8972986BE19E0287770DF51C47C630A53DC6E97
Thanks -Aneesh
Hi Aneesh,
Your relay needs a DirPort to be a fallback directory mirror. (This is an old requirement, we hope to fix it at some point.)
Your DirPort should be on 9030 by default. Or you can configure a DirPort on PORT_NUMBER using:
DirPort PORT_NUMBER
Let us know when you've configured a DirPort, and we'll put your relay on the list.
T
Hey Teor,
Thanks for your reply. I have added my DirPort in torcc as 9030 and restarted my relay. Let me know if you need anything else.
Thanks -Aneesh
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
On 22 Dec 2017, at 22:19, Aneesh Dogra lionaneesh@gmail.com wrote:
Thanks for your reply. I have added my DirPort in torcc as 9030 and restarted my relay. Let me know if you need anything else.
I'm still not seeing a DirPort in Relay Search: https://atlas.torproject.org/#details/D8972986BE19E0287770DF51C47C630A53DC6E...
Do you have AccountingMax set? Then your relay can't be a reliable fallback directory mirror.
Otherwise, please copy and paste the DirPort lines in your torrc, and the messages that Tor logs about your DirPort when it starts up.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
You can throw 867B95CACD64653FEEC4D2CEFC5C49B4620307A7 into the mix - its my only stable server with little load.
I would have IPv6 but OVH AU has some sort of problem - have had a ticket open for two weeks now.
Paul
AA0D167E03E298F9A8CD50F448B81FBD7FA80D56
++ 21/12/17 10:50 +1100 - teor:
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please:
- make sure it has enough available file descriptors, and
- set MaxMemInQueues to the amount of RAM you have available per tor
instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
December 20, 2017 6:51 PM, "teor" teor2345@gmail.com 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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please:
- make sure it has enough available file descriptors, and
- set MaxMemInQueues to the amount of RAM you have available per tor
instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
log [5]: https://lists.torproject.org/pipermail/tor-relays/2017-December/013881.html
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
well, i intend to keep mine up indefinitely (barring the unforeseen) so why not?
2 relays:
D122094E396DF8BA560843E7B983B0EA649B7DF9 E911A899D51036A5D2A9DE0931A0A1E8DA4C6148
thanks.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
On 23 Dec 2017, at 04:09, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
well, i intend to keep mine up indefinitely (barring the unforeseen) so why not?
2 relays:
D122094E396DF8BA560843E7B983B0EA649B7DF9 E911A899D51036A5D2A9DE0931A0A1E8DA4C6148
Hi,
Fallbacks need a DirPort. Please let me know when you've configured one.
For details, see: https://lists.torproject.org/pipermail/tor-relays/2017-December/013927.html
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
On December 22, 2017 5:48:59 PM EST, teor teor2345@gmail.com wrote:
On 23 Dec 2017, at 04:09, Fabian A. Santiago
fsantiago@garbage-juice.com wrote:
well, i intend to keep mine up indefinitely (barring the unforeseen)
so why not?
2 relays:
D122094E396DF8BA560843E7B983B0EA649B7DF9 E911A899D51036A5D2A9DE0931A0A1E8DA4C6148
Hi,
Fallbacks need a DirPort. Please let me know when you've configured one.
For details, see: https://lists.torproject.org/pipermail/tor-relays/2017-December/013927.html
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
Oh I did. But the startup log (journalctl) states since I call AccountingMax in torrc, Tor wouldn't publish it. Didn't even consider that. So deal breaker I suppose? Will it never publish it with that parameter in place? These are new (less than 2 weeks) and I was initially told by the list that it wouldn't get published right away until Tor figures out that my Max value won't be surpassed. They're both on port 80 in my torrc files.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
On December 22, 2017 5:55:16 PM EST, "Fabian A. Santiago" fsantiago@garbage-juice.com wrote:
On December 22, 2017 5:48:59 PM EST, teor teor2345@gmail.com wrote:
On 23 Dec 2017, at 04:09, Fabian A. Santiago
fsantiago@garbage-juice.com wrote:
well, i intend to keep mine up indefinitely (barring the unforeseen)
so why not?
2 relays:
D122094E396DF8BA560843E7B983B0EA649B7DF9 E911A899D51036A5D2A9DE0931A0A1E8DA4C6148
Hi,
Fallbacks need a DirPort. Please let me know when you've configured one.
For details, see: https://lists.torproject.org/pipermail/tor-relays/2017-December/013927.html
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
Oh I did. But the startup log (journalctl) states since I call AccountingMax in torrc, Tor wouldn't publish it. Didn't even consider that. So deal breaker I suppose? Will it never publish it with that parameter in place? These are new (less than 2 weeks) and I was initially told by the list that it wouldn't get published right away until Tor figures out that my Max value won't be surpassed. They're both on port 80 in my torrc files.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I just saw another reply of yours answering my question. Then please disregard my submittal. Sorry.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
I installed those two instances a few days ago, don't know if it's ok but I'd like to be part of this:
8B6556601612F1E2AFCE2A12FFFAF8482A76DD1F 5E363D72488276160D062DDD2DFA25CFEBAF5EA9
On 12/20/2017 04:50 PM, teor 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.
CE24412AD69444954B4015E293AE53DDDAFEA3D6
A bit late to the party but
A53C46F5B157DD83366D45A8E99A244934A14C46
-Jon --
On 4 Jan 2018, at 02:17, Jonathan Proulx jon@csail.mit.edu wrote:
A bit late to the party but
A53C46F5B157DD83366D45A8E99A244934A14C46
Thanks!
There is still time for other operators to opt-in relays. We'll start building the list over the next week or two.
A reminder:
We choose up to 3 relays per operator. And we rotate the relays in the list every release.
Please opt-in as many relays as you would like.
T
-- Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org ------------------------------------------------------------------------
Hi,
I have
4E8CE6F5651E7342C1E7E5ED031E82078134FB0D
running both on IPv4 and IPv6. There seems (seemed?) to be a bit of a disagreement between authority servers when voting for the stable flag regarding IPv6, but manual checks always were fine.
René
2017-12-21 0:50 GMT+01:00 teor teor2345@gmail.com:
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please:
- make sure it has enough available file descriptors, and
- set MaxMemInQueues to the amount of RAM you have available per tor instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
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 [5]: https://lists.torproject.org/pipermail/tor-relays/2017- December/013881.html
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Hi Added two new members to my family
92412EA1B9AA887D462B51D816777002F4D58907 360CBA08D1E24F513162047BDB54A1015E531534
They are few days old and about to be confirmed.
Best regards Anders
Sent with [ProtonMail](https://protonmail.com) Secure Email.
-------- Original Message -------- Subject: Re: [tor-relays] Become a Fallback Directory Mirror Local Time: 4 January 2018 1:39 PM UTC Time: 4 January 2018 12:39 From: r.c.ladan@gmail.com To: tor-relays@lists.torproject.org
Hi,
I have
4E8CE6F5651E7342C1E7E5ED031E82078134FB0D
running both on IPv4 and IPv6. There seems (seemed?) to be a bit of a disagreement between authority servers when voting for the stable flag regarding IPv6, but manual checks always were fine.
René
2017-12-21 0:50 GMT+01:00 teor teor2345@gmail.com:
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please:
- make sure it has enough available file descriptors, and
- set MaxMemInQueues to the amount of RAM you have available per tor instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Fingerprint: A2A6616723B511D8E068BB71705191763191F6B2 Address: 87.118.122.120:443
-------- Original Message -------- Subject: [tor-relays] Become a Fallback Directory Mirror Local Time: 21 December 2017 12:50 AM UTC Time: 20 December 2017 23:50 From: teor2345@gmail.com To: tor-relays@lists.torproject.org
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please:
- make sure it has enough available file descriptors, and
- set MaxMemInQueues to the amount of RAM you have available per tor
instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Normalcitizen: E51620B90DCB310138ED89EDEDD0A5C361AAE24E
-------- Original Message -------- Subject: [tor-relays] Become a Fallback Directory Mirror Local Time: 21 December 2017 12:50 AM UTC Time: 20 December 2017 23:50 From: teor2345@gmail.com To: tor-relays@lists.torproject.org
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please: make sure it has enough available file descriptors, and set MaxMemInQueues to the amount of RAM you have available per tor instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
[1]: https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors [2]: https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc https://gitweb.torproject.org/tor.git/tree/src/or/fallback_dirs.inc [3]: https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist https://gitweb.torproject.org/tor.git/tree/scripts/maint/fallback.whitelist [4]: https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2... https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2017-05-16-0815-09cd78886.log [5]: https://lists.torproject.org/pipermail/tor-relays/2017-December/013881.html https://lists.torproject.org/pipermail/tor-relays/2017-December/013881.html
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
January 8, 2018 3:29 PM, "Spiros Andreou" mail@spiros.io wrote:
Normalcitizen: E51620B90DCB310138ED89EDEDD0A5C361AAE24E
-------- Original Message --------
Subject: [tor-relays] Become a Fallback Directory Mirror
Local Time: 21 December 2017 12:50 AM
UTC Time: 20 December 2017 23:50
From: teor2345@gmail.com
To: tor-relays@lists.torproject.org
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please:
- make sure it has enough available file descriptors, and
- set MaxMemInQueues to the amount of RAM you have available per tor
instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
log [5]: https://lists.torproject.org/pipermail/tor-relays/2017-December/013881.html
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
Hello,
I've moved my relay to an unmetered provider, and intend to keep it up long term. Here you are, if you can still use it:
D122094E396DF8BA560843E7B983B0EA649B7DF9
Thanks.
--
Thanks,
Fabian S.
OpenPGP: 3C3FA072ACCB7AC5DB0F723455502B0EEB9070FC
Hi,
On 22 Jan 2018, at 05:01, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
January 8, 2018 3:29 PM, "Spiros Andreou" mail@spiros.io wrote:
Normalcitizen: E51620B90DCB310138ED89EDEDD0A5C361AAE24E
-------- Original Message --------
Subject: [tor-relays] Become a Fallback Directory Mirror
Local Time: 21 December 2017 12:50 AM
UTC Time: 20 December 2017 23:50
From: teor2345@gmail.com
To: tor-relays@lists.torproject.org
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please:
- make sure it has enough available file descriptors, and
- set MaxMemInQueues to the amount of RAM you have available per tor
instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
log [5]: https://lists.torproject.org/pipermail/tor-relays/2017-December/013881.html
-- Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n
Hello,
I've moved my relay to an unmetered provider, and intend to keep it up long term. Here you are, if you can still use it:
D122094E396DF8BA560843E7B983B0EA649B7DF9
Thanks for running a relay!
Yes, we can use your relay. We will rebuild the list in 6-12 months.
We are keeping track of opt-ins. Yours is here: https://trac.torproject.org/projects/tor/ticket/24805#comment:8
T
Hi,
If it is not too late, I would like to volunteer the relay 32828476F4F84E15C42B4C360A5CD8DE4C3C2BE7.
Rhea
On Sun, Jan 21, 2018 at 1:45 PM teor teor2345@gmail.com wrote:
Hi,
On 22 Jan 2018, at 05:01, Fabian A. Santiago fsantiago@garbage-juice.com wrote:
January 8, 2018 3:29 PM, "Spiros Andreou" mail@spiros.io wrote:
Normalcitizen: E51620B90DCB310138ED89EDEDD0A5C361AAE24E
-------- Original Message --------
Subject: [tor-relays] Become a Fallback Directory Mirror
Local Time: 21 December 2017 12:50 AM
UTC Time: 20 December 2017 23:50
From: teor2345@gmail.com
To: tor-relays@lists.torproject.org
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.
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: What about the current relay DDoS?
We don't think the DDoS will have much impact on the fallback list.
If your relay is affected, please:
make sure it has enough available file descriptors, and
set MaxMemInQueues to the amount of RAM you have available per tor
instance (or maybe a few hundred MB less).
We're also working on some code changes. See [5] for more details.
[4]:
https://trac.torproject.org/projects/tor/attachment/ticket/21564/fallbacks_2...
log
--
Tim / teor
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
Hello,
I've moved my relay to an unmetered provider, and intend to keep it up long term. Here you are, if you can still use it:
D122094E396DF8BA560843E7B983B0EA649B7DF9
Thanks for running a relay!
Yes, we can use your relay. We will rebuild the list in 6-12 months.
We are keeping track of opt-ins. Yours is here: https://trac.torproject.org/projects/tor/ticket/24805#comment:8
T _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 22 Jan 2018, at 11:33, Rhea Tor rhea@nullsky.info wrote:
If it is not too late, I would like to volunteer the relay 32828476F4F84E15C42B4C360A5CD8DE4C3C2BE7.
It's never too late - we rebuild the list every 6-12 months.
We're tracking changes for the next list. Yours is here: https://trac.torproject.org/projects/tor/ticket/24805#comment:9
T
tor-relays@lists.torproject.org
-
Anders Burmeister -
Aneesh Dogra -
Fabian A. Santiago -
Franklin Bynum -
Johan Fleury -
John Ricketts -
Jonathan Proulx -
Kenneth Freeman -
Otheontelth -
Paul Templeton -
Rejo Zenger -
René Ladan -
Rhea Tor -
Spiros Andreou -
teor