-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Dear Tor Relay Operator,
Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0]
These mirrors are hard-coded into tor's source code, like the directory authorities. We have 80 fallbacks, but we want 200 for the next release.
Fallbacks need to have: - - the same IP address(es) and ports for the next 2 years, - - the same relay identity key for the next 2 years, - - good uptime (at least 95%), and - - good bandwidth and network connectivity (we estimate an extra 25GB per month).
Please email me to add your relays that fit these criteria to the list. If you are BCC'd on this email, it looks like you have at least one relay that could become a fallback. You can also email me if you know your relay will be changing address or key, and I'll make sure we don't choose it.
We are keeping the fallback lists from the last release[1][2].
So if you have emailed me before about becoming a fallback, there is no need to email again. But please let me know if your relay details have changed. (I did not BCC relay operators who are already on the fallback lists, unless their relay details changed.)
In a week or two, I will run a script to select the hard-coded list for the release.
If you're interested, here's some background to this request:
The latest list[3] and log[4] of candidates was generated using the instructions in [5] from scripts/maint/updateFallbackDirs.py on my GitHub branch[6]. (This branch has some bug fixes compared to what's in master.) We're tracking this work in [7].
[0]: https://trac.torproject.org/projects/tor/wiki/doc/FallbackDirectoryMirrors [1]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/scripts/maint/fallback... [2]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/scripts/maint/fallback... [3]: https://trac.torproject.org/projects/tor/attachment/ticket/18828/potential_e... [4]: https://trac.torproject.org/projects/tor/attachment/ticket/18828/potential_e... [5]: https://trac.torproject.org/projects/tor/wiki/doc/UpdatingFallbackDirectoryM... [6]: https://github.com/teor2345/tor/blob/fallbacks-029-v2/scripts/maint/updateFa... [7]: https://trac.torproject.org/projects/tor/ticket/18828
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 4 December 2016 at 10:44, teor teor2345@gmail.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Dear Tor Relay Operator,
Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0]
These mirrors are hard-coded into tor's source code, like the directory authorities. We have 80 fallbacks, but we want 200 for the next release.
Fallbacks need to have:
- the same IP address(es) and ports for the next 2 years,
- the same relay identity key for the next 2 years,
- good uptime (at least 95%), and
(we estimate an extra 25GB per month).
- good bandwidth and network connectivity
Please email me to add your relays that fit these criteria to the list.
Hi, I believe I already have 3 relays in the list but have added some more since
This one probably qualifies https://atlas.torproject.org/#details/9C900A7F6F5DD034CFFD192DAEC9CCAA813DB0...
Others may too young to trust the hosting with future uptime https://atlas.torproject.org/#details/A0E3D30A660DB70CA0B6D081BA54D094DED6F2... https://atlas.torproject.org/#details/674DCBB0D9C1C4C4DBFB4A9AE024AF59FE4E7F...
If you are BCC'd on this email, it looks like you have at least one relay that could become a fallback. You can also email me if you know your relay will be changing address or key, and I'll make sure we don't choose it.
We are keeping the fallback lists from the last release[1][2].
So if you have emailed me before about becoming a fallback, there is no need to email again. But please let me know if your relay details have changed. (I did not BCC relay operators who are already on the fallback lists, unless their relay details changed.)
In a week or two, I will run a script to select the hard-coded list for the release.
If you're interested, here's some background to this request:
The latest list[3] and log[4] of candidates was generated using the instructions in [5] from scripts/maint/updateFallbackDirs.py on my GitHub branch[6]. (This branch has some bug fixes compared to what's in master.) We're tracking this work in [7].
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
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJYQ+laAAoJEEUMun+WjwlLXd8QAMVKWrGW+N5ij5/1k1AEDQpC qMK3C3stukeuHYqLEU3GnhJFU/CWMp+iThRNueC5I96MEpcioJDQaCDK6aGEvTY3 efPnYwOJcgE7v4up+JSFWUlO4HcF5Fu5cSVl710JjRiHuZAyLOQw0rWEMzfp0OQp sZLgijbtCUCcels7IS+bE89y4KKQvLu5lz+H7cPIcsx4TJ4QHd5LbWuvtNIHE2lW zA3LlrYsO4vtrFs/0kBWku1u7l1ZhD0Un/lwY7JWaxGmwm9C6kJDFwBFCGYRlakF VLfsoVSgcdjQPkZV9jeL0X+9Wn9L6zZ5JNhM5lhYYpGVD+Rl/apPfhxHI5aOTsGe WRcDjxvgUdMD//xnk2XTmnzKCNUNMyUKGSL8Y7Fadp7+dLLkWlovEp6iOnyAffh1 ZnrV7dhRgH3NcgACDpQ2rAqVzUnhdn1//bcD1MlXjObxvZD1Io1zp7CDQHnG6IaG ydc+3qoqUoII0JQFxrRCFi2cH/E8+3x0+7fC0g91irdGG+Pcosf7IFPJvFsdilCg rN4n6Ohmm1L3KQVWLG7TcvEAcjIeyMurhCvK042Q/X7HYenVS3wVxawd8dnb/rOl 0ItMUsXBKgLVcZXhzUTOB+pNaX8aFj1sJnCB2LRDT8s8a2+zESufNxjgGYZ3Nduk FziDqhHJs7MXyX0HPJPH =omox -----END PGP SIGNATURE-----
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 4 Dec. 2016, at 22:06, Pascal Terjan pterjan@gmail.com wrote:
On 4 December 2016 at 10:44, teor teor2345@gmail.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Dear Tor Relay Operator,
Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0]
These mirrors are hard-coded into tor's source code, like the directory authorities. We have 80 fallbacks, but we want 200 for the next release.
Fallbacks need to have:
- the same IP address(es) and ports for the next 2 years,
- the same relay identity key for the next 2 years,
- good uptime (at least 95%), and
- good bandwidth and network connectivity
(we estimate an extra 25GB per month).
Please email me to add your relays that fit these criteria to the list.
Hi, I believe I already have 3 relays in the list but have added some more since
This one probably qualifies https://atlas.torproject.org/#details/9C900A7F6F5DD034CFFD192DAEC9CCAA813DB0...
Thanks!
It needs a DirPort, let me know if you want to add one and I'll put it on the list. (It will need to keep the DirPort for 6 months, so the earliest it would get in is 0.3.0 or 0.3.1.)
Others may too young to trust the hosting with future uptime https://atlas.torproject.org/#details/A0E3D30A660DB70CA0B6D081BA54D094DED6F2... https://atlas.torproject.org/#details/674DCBB0D9C1C4C4DBFB4A9AE024AF59FE4E7F...
Let me know when they've been around long enough, and I'll add them. (The first one will need a DirPort, why not add it now?)
T
On 4 Dec. 2016, at 22:18, teor teor2345@gmail.com wrote:
On 4 Dec. 2016, at 22:06, Pascal Terjan pterjan@gmail.com wrote:
On 4 December 2016 at 10:44, teor teor2345@gmail.com wrote:
...
Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0]
...
Please email me to add your relays that fit these criteria to the list.
Hi, I believe I already have 3 relays in the list but have added some more since
This one probably qualifies https://atlas.torproject.org/#details/9C900A7F6F5DD034CFFD192DAEC9CCAA813DB0...
Thanks!
It needs a DirPort, let me know if you want to add one and I'll put it on the list. (It will need to keep the DirPort for 6 months, so the earliest it would get in is 0.3.0 or 0.3.1.)
Sorry, I was wrong here: the OnionOO address stability only gets reset when you *remove* an address and port. So add a DirPort, and your relay will be fine as a fallback.
T
On 4 December 2016 at 14:20, teor teor2345@gmail.com wrote:
On 4 Dec. 2016, at 22:18, teor teor2345@gmail.com wrote:
On 4 Dec. 2016, at 22:06, Pascal Terjan pterjan@gmail.com wrote:
On 4 December 2016 at 10:44, teor teor2345@gmail.com wrote:
...
Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0]
...
Please email me to add your relays that fit these criteria to the list.
Hi, I believe I already have 3 relays in the list but have added some more since
This one probably qualifies https://atlas.torproject.org/#details/9C900A7F6F5DD034CFFD192DAEC9CCAA813DB0...
Thanks!
It needs a DirPort, let me know if you want to add one and I'll put it on the list. (It will need to keep the DirPort for 6 months, so the earliest it would get in is 0.3.0 or 0.3.1.)
Sorry, I was wrong here: the OnionOO address stability only gets reset when you *remove* an address and port. So add a DirPort, and your relay will be fine as a fallback.
Done, I should really use some template when adding new relays to not forget such things :)
On 5 Dec. 2016, at 02:55, Pascal Terjan pterjan@gmail.com wrote:
On 4 December 2016 at 14:20, teor teor2345@gmail.com wrote:
On 4 Dec. 2016, at 22:18, teor teor2345@gmail.com wrote:
On 4 Dec. 2016, at 22:06, Pascal Terjan pterjan@gmail.com wrote:
On 4 December 2016 at 10:44, teor teor2345@gmail.com wrote:
...
Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0]
...
Please email me to add your relays that fit these criteria to the list.
Hi, I believe I already have 3 relays in the list but have added some more since
This one probably qualifies https://atlas.torproject.org/#details/9C900A7F6F5DD034CFFD192DAEC9CCAA813DB0...
Thanks!
It needs a DirPort, let me know if you want to add one and I'll put it on the list. (It will need to keep the DirPort for 6 months, so the earliest it would get in is 0.3.0 or 0.3.1.)
Sorry, I was wrong here: the OnionOO address stability only gets reset when you *remove* an address and port. So add a DirPort, and your relay will be fine as a fallback.
Done, I should really use some template when adding new relays to not forget such things :)
Thanks, fixed!
T
Tim,
Did you receive email from me directly to your gmail account?
John
On Dec 4, 2016, at 04:45, teor teor2345@gmail.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Dear Tor Relay Operator,
Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0]
These mirrors are hard-coded into tor's source code, like the directory authorities. We have 80 fallbacks, but we want 200 for the next release.
Fallbacks need to have:
- the same IP address(es) and ports for the next 2 years,
- the same relay identity key for the next 2 years,
- good uptime (at least 95%), and
- good bandwidth and network connectivity
(we estimate an extra 25GB per month).
Please email me to add your relays that fit these criteria to the list. If you are BCC'd on this email, it looks like you have at least one relay that could become a fallback. You can also email me if you know your relay will be changing address or key, and I'll make sure we don't choose it.
We are keeping the fallback lists from the last release[1][2].
So if you have emailed me before about becoming a fallback, there is no need to email again. But please let me know if your relay details have changed. (I did not BCC relay operators who are already on the fallback lists, unless their relay details changed.)
In a week or two, I will run a script to select the hard-coded list for the release.
If you're interested, here's some background to this request:
The latest list[3] and log[4] of candidates was generated using the instructions in [5] from scripts/maint/updateFallbackDirs.py on my GitHub branch[6]. (This branch has some bug fixes compared to what's in master.) We're tracking this work in [7].
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
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJYQ+laAAoJEEUMun+WjwlLXd8QAMVKWrGW+N5ij5/1k1AEDQpC qMK3C3stukeuHYqLEU3GnhJFU/CWMp+iThRNueC5I96MEpcioJDQaCDK6aGEvTY3 efPnYwOJcgE7v4up+JSFWUlO4HcF5Fu5cSVl710JjRiHuZAyLOQw0rWEMzfp0OQp sZLgijbtCUCcels7IS+bE89y4KKQvLu5lz+H7cPIcsx4TJ4QHd5LbWuvtNIHE2lW zA3LlrYsO4vtrFs/0kBWku1u7l1ZhD0Un/lwY7JWaxGmwm9C6kJDFwBFCGYRlakF VLfsoVSgcdjQPkZV9jeL0X+9Wn9L6zZ5JNhM5lhYYpGVD+Rl/apPfhxHI5aOTsGe WRcDjxvgUdMD//xnk2XTmnzKCNUNMyUKGSL8Y7Fadp7+dLLkWlovEp6iOnyAffh1 ZnrV7dhRgH3NcgACDpQ2rAqVzUnhdn1//bcD1MlXjObxvZD1Io1zp7CDQHnG6IaG ydc+3qoqUoII0JQFxrRCFi2cH/E8+3x0+7fC0g91irdGG+Pcosf7IFPJvFsdilCg rN4n6Ohmm1L3KQVWLG7TcvEAcjIeyMurhCvK042Q/X7HYenVS3wVxawd8dnb/rOl 0ItMUsXBKgLVcZXhzUTOB+pNaX8aFj1sJnCB2LRDT8s8a2+zESufNxjgGYZ3Nduk FziDqhHJs7MXyX0HPJPH =omox -----END PGP SIGNATURE-----
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 5 Dec. 2016, at 08:21, John Ricketts john@quintex.com wrote:
Tim,
Did you receive email from me directly to your gmail account?
John
Hi John (and others),
I just emailed about a hundred relay operators individually, as well as the ~1700 on this list.
I will respond to every reply I get.
But please give me at least 3 days to respond before checking again.
T
Hey Tim,
I believe my relay may already be on the fallback list. If not, please feel free to include it. It has been up, fast and stable for well over 2 years and will up for the indefinite future at this time.
Thanks
On Sun, Dec 4, 2016 at 5:44 AM, teor teor2345@gmail.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Dear Tor Relay Operator,
Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0]
These mirrors are hard-coded into tor's source code, like the directory authorities. We have 80 fallbacks, but we want 200 for the next release.
Fallbacks need to have:
- the same IP address(es) and ports for the next 2 years,
- the same relay identity key for the next 2 years,
- good uptime (at least 95%), and
(we estimate an extra 25GB per month).
- good bandwidth and network connectivity
Please email me to add your relays that fit these criteria to the list. If you are BCC'd on this email, it looks like you have at least one relay that could become a fallback. You can also email me if you know your relay will be changing address or key, and I'll make sure we don't choose it.
We are keeping the fallback lists from the last release[1][2].
So if you have emailed me before about becoming a fallback, there is no need to email again. But please let me know if your relay details have changed. (I did not BCC relay operators who are already on the fallback lists, unless their relay details changed.)
In a week or two, I will run a script to select the hard-coded list for the release.
If you're interested, here's some background to this request:
The latest list[3] and log[4] of candidates was generated using the instructions in [5] from scripts/maint/updateFallbackDirs.py on my GitHub branch[6]. (This branch has some bug fixes compared to what's in master.) We're tracking this work in [7].
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
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJYQ+laAAoJEEUMun+WjwlLXd8QAMVKWrGW+N5ij5/1k1AEDQpC qMK3C3stukeuHYqLEU3GnhJFU/CWMp+iThRNueC5I96MEpcioJDQaCDK6aGEvTY3 efPnYwOJcgE7v4up+JSFWUlO4HcF5Fu5cSVl710JjRiHuZAyLOQw0rWEMzfp0OQp sZLgijbtCUCcels7IS+bE89y4KKQvLu5lz+H7cPIcsx4TJ4QHd5LbWuvtNIHE2lW zA3LlrYsO4vtrFs/0kBWku1u7l1ZhD0Un/lwY7JWaxGmwm9C6kJDFwBFCGYRlakF VLfsoVSgcdjQPkZV9jeL0X+9Wn9L6zZ5JNhM5lhYYpGVD+Rl/apPfhxHI5aOTsGe WRcDjxvgUdMD//xnk2XTmnzKCNUNMyUKGSL8Y7Fadp7+dLLkWlovEp6iOnyAffh1 ZnrV7dhRgH3NcgACDpQ2rAqVzUnhdn1//bcD1MlXjObxvZD1Io1zp7CDQHnG6IaG ydc+3qoqUoII0JQFxrRCFi2cH/E8+3x0+7fC0g91irdGG+Pcosf7IFPJvFsdilCg rN4n6Ohmm1L3KQVWLG7TcvEAcjIeyMurhCvK042Q/X7HYenVS3wVxawd8dnb/rOl 0ItMUsXBKgLVcZXhzUTOB+pNaX8aFj1sJnCB2LRDT8s8a2+zESufNxjgGYZ3Nduk FziDqhHJs7MXyX0HPJPH =omox -----END PGP SIGNATURE-----
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 7 Dec. 2016, at 11:04, l3thal.injecti0n@gmail.com wrote:
Hey Tim,
I believe my relay may already be on the fallback list. If not, please feel free to include it. It has been up, fast and stable for well over 2 years and will up for the indefinite future at this time.
Thanks, I added your relay to the whitelist.
TorWeatherHelper - 0F100F60C7A63BED90216052324D29B08CFCF797
I'll run the script later in December that generates a list of relays for the release.
Tim
Thanks
On Sun, Dec 4, 2016 at 5:44 AM, teor teor2345@gmail.com wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Dear Tor Relay Operator,
Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0]
These mirrors are hard-coded into tor's source code, like the directory authorities. We have 80 fallbacks, but we want 200 for the next release.
Fallbacks need to have:
- the same IP address(es) and ports for the next 2 years,
- the same relay identity key for the next 2 years,
- good uptime (at least 95%), and
- good bandwidth and network connectivity
(we estimate an extra 25GB per month).
Please email me to add your relays that fit these criteria to the list. If you are BCC'd on this email, it looks like you have at least one relay that could become a fallback. You can also email me if you know your relay will be changing address or key, and I'll make sure we don't choose it.
We are keeping the fallback lists from the last release[1][2].
So if you have emailed me before about becoming a fallback, there is no need to email again. But please let me know if your relay details have changed. (I did not BCC relay operators who are already on the fallback lists, unless their relay details changed.)
In a week or two, I will run a script to select the hard-coded list for the release.
If you're interested, here's some background to this request:
The latest list[3] and log[4] of candidates was generated using the instructions in [5] from scripts/maint/updateFallbackDirs.py on my GitHub branch[6]. (This branch has some bug fixes compared to what's in master.) We're tracking this work in [7].
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
-----BEGIN PGP SIGNATURE----- Comment: GPGTools - https://gpgtools.org
iQIcBAEBCgAGBQJYQ+laAAoJEEUMun+WjwlLXd8QAMVKWrGW+N5ij5/1k1AEDQpC qMK3C3stukeuHYqLEU3GnhJFU/CWMp+iThRNueC5I96MEpcioJDQaCDK6aGEvTY3 efPnYwOJcgE7v4up+JSFWUlO4HcF5Fu5cSVl710JjRiHuZAyLOQw0rWEMzfp0OQp sZLgijbtCUCcels7IS+bE89y4KKQvLu5lz+H7cPIcsx4TJ4QHd5LbWuvtNIHE2lW zA3LlrYsO4vtrFs/0kBWku1u7l1ZhD0Un/lwY7JWaxGmwm9C6kJDFwBFCGYRlakF VLfsoVSgcdjQPkZV9jeL0X+9Wn9L6zZ5JNhM5lhYYpGVD+Rl/apPfhxHI5aOTsGe WRcDjxvgUdMD//xnk2XTmnzKCNUNMyUKGSL8Y7Fadp7+dLLkWlovEp6iOnyAffh1 ZnrV7dhRgH3NcgACDpQ2rAqVzUnhdn1//bcD1MlXjObxvZD1Io1zp7CDQHnG6IaG ydc+3qoqUoII0JQFxrRCFi2cH/E8+3x0+7fC0g91irdGG+Pcosf7IFPJvFsdilCg rN4n6Ohmm1L3KQVWLG7TcvEAcjIeyMurhCvK042Q/X7HYenVS3wVxawd8dnb/rOl 0ItMUsXBKgLVcZXhzUTOB+pNaX8aFj1sJnCB2LRDT8s8a2+zESufNxjgGYZ3Nduk FziDqhHJs7MXyX0HPJPH =omox -----END PGP SIGNATURE-----
tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
-- Good code is like a good joke - it needs no explanation. -- Russ Olsen _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
T
Hey teor,
my relay 5665A3904C89E22E971305EE8C1997BCA4123C69 is according to your log [4] black and whitelisted. But it is only in the whitelist from you [1] My second relay B567E8E39641F61091C1F2CAAAF73D3D1BF9CFE1 is according to [4] blacklisted but also not in [2].
I hope you can clarify this out.
Best Regards Tobias
Am 04.12.2016 um 11:44 schrieb teor:
Dear Tor Relay Operator,
Your relay(s) can help tor clients find the tor network by becoming a fallback directory mirror.[0]
These mirrors are hard-coded into tor's source code, like the directory authorities. We have 80 fallbacks, but we want 200 for the next release.
Fallbacks need to have:
- the same IP address(es) and ports for the next 2 years,
- the same relay identity key for the next 2 years,
- good uptime (at least 95%), and
- good bandwidth and network connectivity (we estimate an extra 25GB per month).
Please email me to add your relays that fit these criteria to the list. If you are BCC'd on this email, it looks like you have at least one relay that could become a fallback. You can also email me if you know your relay will be changing address or key, and I'll make sure we don't choose it.
We are keeping the fallback lists from the last release[1][2].
So if you have emailed me before about becoming a fallback, there is no need to email again. But please let me know if your relay details have changed. (I did not BCC relay operators who are already on the fallback lists, unless their relay details changed.)
In a week or two, I will run a script to select the hard-coded list for the release.
If you're interested, here's some background to this request:
The latest list[3] and log[4] of candidates was generated using the instructions in [5] from scripts/maint/updateFallbackDirs.py on my GitHub branch[6]. (This branch has some bug fixes compared to what's in master.) We're tracking this work in [7].
T
_______________________________________________ > tor-relays mailing
list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 7 Dec. 2016, at 11:38, Tobias Sachs knight@germancraft.net wrote:
Hey teor,
my relay 5665A3904C89E22E971305EE8C1997BCA4123C69 is according to your log [4] black and whitelisted. But it is only in the whitelist from you [1] My second relay B567E8E39641F61091C1F2CAAAF73D3D1BF9CFE1 is according to [4] blacklisted but also not in [2].
I hope you can clarify this out.
Best Regards Tobias
Hi Tobias,
Sorry about the confusion.
I tried to skip relay operators who had responded already. So I temporarily added all the whitelist to the blacklist. This makes it look like lots of relays are in the blacklist, when they are really in the whitelist.
5665A3904C89E22E971305EE8C1997BCA4123C69 is in the whitelist: https://github.com/teor2345/tor/blob/fallbacks-029-v2/scripts/maint/fallback...
5665A3904C89E22E971305EE8C1997BCA4123C69 and B567E8E39641F61091C1F2CAAAF73D3D1BF9CFE1 are not in the blacklist: https://github.com/teor2345/tor/blob/fallbacks-029-v2/scripts/maint/fallback...
Do you want me to add B567E8E39641F61091C1F2CAAAF73D3D1BF9CFE1 to the whitelist? Will it have the same IP and key for the next 2 years?
Also, I tried replying to your direct email, but your mail server was down:
Technical details of temporary failure: The recipient server did not accept our requests to connect. Learn more at https://support.google.com/mail/answer/7720 [mail.germancraft.net. 2a00:f826:8:1::135: timed out] [mail.germancraft.net. 31.47.238.135: generic::failed_precondition: connect error (0): error]
Tim
Am 04.12.2016 um 11:44 schrieb teor:
...
We are keeping the fallback lists from the last release[1][2].
...
The latest list[3] and log[4] of candidates was generated using the instructions in [5] from scripts/maint/updateFallbackDirs.py on my GitHub branch[6]. (This branch has some bug fixes compared to what's in master.) We're tracking this work in [7].
T
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
T
tor-relays@lists.torproject.org
-
John Ricketts -
l3thal.injecti0n＠gmail.com -
Pascal Terjan -
teor -
Tobias Sachs