nihilist/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2024-11-11 21:53:48 +01:00
Code Issues Packages Projects Releases Wiki Activity
a403230fe3
tor/src/or/fallback_dirs.inc

266 lines
12 KiB
PHP
Raw Normal View History

Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
/* To comment-out entries in this file, use C comments, and add * to the start of each line. (stem finds fallback entries using " at the start of a line.) */
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
/* Whitelist & blacklist excluded 1273 of 1553 candidates. */
/* Checked IPv4 DirPorts served a consensus within 15.0s. */
Add default fallback directories for the 0.2.8 alpha releases Allow fallback directories which have been stable for 30 days to work around #18050, which causes relays to submit descriptors with 0 DirPorts when restarted. (Particularly during Tor version upgrades.) Ignore low fallback directory count in alpha builds.
2016-01-18 02:34:34 +01:00
/*
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
Final Count: 100 (Eligible 280, Target 356 (1781 * 0.20), Max 100)
Excluded: 180 (Same Operator 102, Failed/Skipped Download 40, Excess 38)
Bandwidth Range: 6.0 - 67.2 MB/s
Add default fallback directories for the 0.2.8 alpha releases Allow fallback directories which have been stable for 30 days to work around #18050, which causes relays to submit descriptors with 0 DirPorts when restarted. (Particularly during Tor version upgrades.) Ignore low fallback directory count in alpha builds.
2016-01-18 02:34:34 +01:00
*/
/*
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
Onionoo Source: details Date: 2016-04-18 01:00:00 Version: 3.1
URL: https:onionoo.torproject.orgdetails?fields=fingerprint%2Cnickname%2Ccontact%2Clast_changed_address_or_port%2Cconsensus_weight%2Cadvertised_bandwidth%2Cor_addresses%2Cdir_address%2Crecommended_version%2Cflags%2Ceffective_family&flag=V2Dir&type=relay&last_seen_days=-7&first_seen_days=7-
Add default fallback directories for the 0.2.8 alpha releases Allow fallback directories which have been stable for 30 days to work around #18050, which causes relays to submit descriptors with 0 DirPorts when restarted. (Particularly during Tor version upgrades.) Ignore low fallback directory count in alpha builds.
2016-01-18 02:34:34 +01:00
*/
/*
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
Onionoo Source: uptime Date: 2016-04-18 01:00:00 Version: 3.1
URL: https:onionoo.torproject.orguptime?first_seen_days=7-&flag=V2Dir&type=relay&last_seen_days=-7
Add default fallback directories for the 0.2.8 alpha releases Allow fallback directories which have been stable for 30 days to work around #18050, which causes relays to submit descriptors with 0 DirPorts when restarted. (Particularly during Tor version upgrades.) Ignore low fallback directory count in alpha builds.
2016-01-18 02:34:34 +01:00
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"193.171.202.146:9030 orport=9001 id=01A9258A46E97FF8B2CAC7910577862C14F2C524"
" weight=10",
"5.9.110.236:9030 orport=9001 id=0756B7CD4DFC8182BE23143FAC0642F515182CEB"
" ipv6=[2a01:4f8:162:51e2::2]:9001"
" weight=10",
Remove a fallback that was on the hardcoded list, then opted-out The fallback was added in 0.2.8.2-alpha.
2016-07-29 02:00:49 +02:00
/* Fallback was on 0.2.8.2-alpha list, but opted-out before 0.2.8.6
* "37.187.1.149:9030 orport=9001 id=08DC0F3C6E3D9C527C1FC8745D35DD1B0DE1875D"
* " ipv6=[2001:41d0:a:195::1]:9001"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"5.39.92.199:80 orport=443 id=0BEA4A88D069753218EAAAD6D22EA87B9A1319D6"
" weight=10",
"5.196.88.122:9030 orport=9001 id=0C2C599AFCB26F5CFC2C7592435924C1D63D9484"
" weight=10",
"178.62.197.82:80 orport=443 id=0D3EBA17E1C78F1E9900BABDB23861D46FCAF163"
" weight=10",
"144.76.14.145:110 orport=143 id=14419131033443AE6E21DA82B0D307F7CAE42BDB"
" ipv6=[2a01:4f8:190:9490::dead]:443"
" weight=10",
"178.32.216.146:9030 orport=9001 id=17898F9A2EBC7D69DAF87C00A1BD2FABF3C9E1D2"
" weight=10",
"46.101.151.222:80 orport=443 id=1DBAED235E3957DE1ABD25B4206BE71406FB61F8"
" weight=10",
"91.219.237.229:80 orport=443 id=1ECD73B936CB6E6B3CD647CC204F108D9DF2C9F7"
" weight=10",
"212.47.229.2:9030 orport=9001 id=20462CBA5DA4C2D963567D17D0B7249718114A68"
" weight=10",
"185.61.138.18:8080 orport=4443 id=2541759BEC04D37811C2209A88E863320271EC9C"
" weight=10",
Remove and blacklist 3 fallbacks which disappeared Blacklist them in case they appear again.
2016-06-22 04:09:32 +02:00
/* Fallback was on 0.2.8.2-alpha list, but went down before 0.2.8.5
Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
* "51.254.215.121:80 orport=443 id=262B66AD25C79588AD1FC8ED0E966395B47E5C1D"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"194.150.168.79:11112 orport=11111 id=29F1020B94BE25E6BE1AD13E93CE19D2131B487C"
" weight=10",
"144.76.26.175:9012 orport=9011 id=2BA2C8E96B2590E1072AECE2BDB5C48921BF8510"
" weight=10",
Update default fallback directories for 0.2.8.2-alpha (Feb 2016) Allow fallback directories which have been stable for 7 days to work around #18050, which causes relays to submit descriptors with 0 DirPorts when restarted. (Particularly during Tor version upgrades.) Ignore low fallback directory count in alpha builds. Set the target count to 50.
2016-02-18 13:03:35 +01:00
"62.210.124.124:9130 orport=9101 id=2EBD117806EE43C3CC885A8F1E4DC60F207E7D3E"
" ipv6=[2001:bc8:3f23:100::1]:9101"
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
" weight=10",
"213.61.66.118:9031 orport=9001 id=30648BC64CEDB3020F4A405E4AB2A6347FB8FA22"
" weight=10",
"212.83.154.33:8080 orport=8443 id=322C6E3A973BC10FC36DE3037AD27BC89F14723B"
" weight=10",
"109.105.109.162:52860 orport=60784 id=32EE911D968BE3E016ECA572BB1ED0A9EE43FC2F"
" ipv6=[2001:948:7:2::163]:5001"
" weight=10",
"146.0.32.144:9030 orport=9001 id=35E8B344F661F4F2E68B17648F35798B44672D7E"
" weight=10",
"217.79.190.25:9030 orport=9090 id=361D33C96D0F161275EE67E2C91EE10B276E778B"
" weight=10",
"62.210.92.11:9130 orport=9101 id=387B065A38E4DAA16D9D41C2964ECBC4B31D30FF"
" ipv6=[2001:bc8:338c::1]:9101"
" weight=10",
"198.50.191.95:80 orport=443 id=39F096961ED2576975C866D450373A9913AFDC92"
" weight=10",
"164.132.77.175:9030 orport=9001 id=3B33F6FCA645AD4E91428A3AF7DC736AD9FB727B"
" weight=10",
"176.10.107.180:9030 orport=9001 id=3D7E274A87D9A89AF064C13D1EE4CA1F184F2600"
" weight=10",
"37.187.102.186:9030 orport=9001 id=489D94333DF66D57FFE34D9D59CC2D97E2CB0053"
" ipv6=[2001:41d0:a:26ba::1]:9001"
" weight=10",
"188.165.194.195:9030 orport=9001 id=49E7AD01BB96F6FE3AB8C3B15BD2470B150354DF"
" weight=10",
"108.53.208.157:80 orport=443 id=4F0DB7E687FC7C0AE55C8F243DA8B0EB27FBF1F2"
" weight=10",
"212.51.134.123:9030 orport=9001 id=50586E25BE067FD1F739998550EDDCB1A14CA5B2"
" ipv6=[2a02:168:6e00:0:3a60:77ff:fe9c:8bd1]:9001"
" weight=10",
"5.175.233.86:80 orport=443 id=5525D0429BFE5DC4F1B0E9DE47A4CFA169661E33"
" weight=10",
"94.23.204.175:9030 orport=9001 id=5665A3904C89E22E971305EE8C1997BCA4123C69"
" weight=10",
"109.163.234.9:80 orport=443 id=5714542DCBEE1DD9864824723638FD44B2122CEA"
" weight=10",
"185.21.100.50:9030 orport=9001 id=58ED9C9C35E433EE58764D62892B4FFD518A3CD0"
" ipv6=[2a00:1158:2:cd00:0:74:6f:72]:443"
" weight=10",
"78.142.142.246:80 orport=443 id=5A5E03355C1908EBF424CAF1F3ED70782C0D2F74"
" weight=10",
Remove and blacklist 3 fallbacks which disappeared Blacklist them in case they appear again.
2016-06-22 04:09:32 +02:00
/* Fallback was on 0.2.8.2-alpha list, but went down before 0.2.8.5
Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
* "185.100.85.138:80 orport=46356 id=5C4DF16A0029CC4F67D3E127356E68F219269859"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"178.16.208.62:80 orport=443 id=5CF8AFA5E4B0BB88942A44A3F3AAE08C3BDFD60B"
" ipv6=[2a00:1c20:4089:1234:a6a4:2926:d0af:dfee]:443"
" weight=10",
"95.128.43.164:80 orport=443 id=616081EC829593AF4232550DE6FFAA1D75B37A90"
" ipv6=[2a02:ec0:209:10::4]:443"
" weight=10",
"89.187.142.208:80 orport=443 id=64186650FFE4469EBBE52B644AE543864D32F43C"
" weight=10",
"144.76.73.140:9030 orport=9001 id=6A640018EABF3DA9BAD9321AA37C2C87BBE1F907"
" weight=10",
"94.126.23.174:9030 orport=9001 id=6FC6F08270D565BE89B7C819DD8E2D487397C073"
" weight=10",
"176.31.191.26:9030 orport=9001 id=7350AB9ED7568F22745198359373C04AC783C37C"
" weight=10",
"46.101.237.246:9030 orport=9001 id=75F1992FD3F403E9C082A5815EB5D12934CDF46C"
" ipv6=[2a03:b0c0:3:d0::208:5001]:9050"
" weight=10",
"185.11.180.67:80 orport=9001 id=794D8EA8343A4E820320265D05D4FA83AB6D1778"
" weight=10",
"62.210.129.246:80 orport=443 id=79E169B25E4C7CE99584F6ED06F379478F23E2B8"
" weight=10",
"82.223.21.74:9030 orport=9001 id=7A32C9519D80CA458FC8B034A28F5F6815649A98"
" ipv6=[2001:470:53e0::cafe]:9050"
" weight=10",
"192.160.102.164:80 orport=9001 id=823AA81E277F366505545522CEDC2F529CE4DC3F"
" weight=10",
"192.87.28.82:9030 orport=9001 id=844AE9CAD04325E955E2BE1521563B79FE7094B7"
" weight=10",
Remove and blacklist 4 fallbacks which are unsuitable Remove a fallback that changed its fingerprint after it was listed This happened after to a software update: https://lists.torproject.org/pipermail/tor-relays/2016-June/009473.html Remove a fallback that changed IPv4 address Remove two fallbacks that were slow to deliver consensuses, we can't guarantee they'll be fast in future. Blacklist all these fallbacks until operators confirm they're stable.
2016-06-22 01:59:05 +02:00
/* Fallback was on 0.2.8.2-alpha list, but changed address before 0.2.8.5
Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
* "84.219.173.60:9030 orport=443 id=855BC2DABE24C861CD887DB9B2E950424B49FC34"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"163.172.138.22:80 orport=443 id=8664DC892540F3C789DB37008236C096C871734D"
" weight=10",
Remove and blacklist 4 fallbacks which are unsuitable Remove a fallback that changed its fingerprint after it was listed This happened after to a software update: https://lists.torproject.org/pipermail/tor-relays/2016-June/009473.html Remove a fallback that changed IPv4 address Remove two fallbacks that were slow to deliver consensuses, we can't guarantee they'll be fast in future. Blacklist all these fallbacks until operators confirm they're stable.
2016-06-22 01:59:05 +02:00
/* Fallback was on 0.2.8.2-alpha list, but downloads were slow before 0.2.8.5
Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
* "185.96.88.29:80 orport=443 id=86C281AD135058238D7A337D546C902BE8505DDE"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"93.180.156.84:9030 orport=9001 id=8844D87E9B038BE3270938F05AF797E1D3C74C0F"
" weight=10",
Remove a fallback that changed DirPort The operator has confirmed that the DirPort change is perament. The relay will be reconsidered as a fallback in 0.2.9.
2016-06-23 02:38:03 +02:00
/* Fallback was on 0.2.8.2-alpha list, but DirPort changed before 0.2.8.5
Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
* "178.217.184.32:9030 orport=443 id=8B7F47AE1A5D954A3E58ACDE0865D09DBA5B738D"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"151.80.42.103:9030 orport=9001 id=9007C1D8E4F03D506A4A011B907A9E8D04E3C605"
" ipv6=[2001:41d0:e:f67::114]:9001"
" weight=10",
"5.79.68.161:81 orport=443 id=9030DCF419F6E2FBF84F63CBACBA0097B06F557E"
" ipv6=[2001:1af8:4700:a012:1::1]:443"
" weight=10",
"51.255.41.65:9030 orport=9001 id=9231DF741915AA1630031A93026D88726877E93A"
" weight=10",
"91.219.237.244:80 orport=443 id=92ECC9E0E2AF81BB954719B189AC362E254AD4A5"
" weight=10",
Remove and blacklist 4 fallbacks which are unsuitable Remove a fallback that changed its fingerprint after it was listed This happened after to a software update: https://lists.torproject.org/pipermail/tor-relays/2016-June/009473.html Remove a fallback that changed IPv4 address Remove two fallbacks that were slow to deliver consensuses, we can't guarantee they'll be fast in future. Blacklist all these fallbacks until operators confirm they're stable.
2016-06-22 01:59:05 +02:00
/* Fallback was on 0.2.8.2-alpha list, but changed fingerprint before 0.2.8.5
Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
* "46.101.102.71:80 orport=443 id=9504CB22EEB25D344DE63CB7A6F2C46F895C3686"
* " ipv6=[2a03:b0c0:3:d0::2ed:7001]:9050"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"85.214.206.219:9030 orport=9001 id=98F8D5F359949E41DE8DF3DBB1975A86E96A84A0"
" weight=10",
"81.7.10.93:31336 orport=31337 id=99E246DB480B313A3012BC3363093CC26CD209C7"
" weight=10",
"46.28.110.244:80 orport=443 id=9F7D6E6420183C2B76D3CE99624EBC98A21A967E"
" weight=10",
"46.165.230.5:80 orport=443 id=A0F06C2FADF88D3A39AA3072B406F09D7095AC9E"
" weight=10",
"171.25.193.77:80 orport=443 id=A10C4F666D27364036B562823E5830BC448E046A"
" ipv6=[2001:67c:289c:3::77]:443"
" weight=10",
"176.9.5.116:9030 orport=9001 id=A1EB8D8F1EE28DB98BBB1EAA3B4BEDD303BAB911"
" weight=10",
"192.34.63.137:9030 orport=443 id=ABCB4965F1FEE193602B50A365425105C889D3F8"
" weight=10",
Remove 2 fallbacks: one lost guard, the other had bad uptime Leave these fallbacks in the whitelist, they may improve before 0.2.9.
2016-06-22 03:33:00 +02:00
/* Fallback was on 0.2.8.2-alpha list, but had low uptime before 0.2.8.5
Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
* "195.154.164.243:80 orport=443 id=AC66FFA4AB35A59EBBF5BF4C70008BF24D8A7A5C"
* " ipv6=[2001:bc8:399f:f000::1]:993"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"86.59.119.88:80 orport=443 id=ACD889D86E02EDDAB1AFD81F598C0936238DC6D0"
" weight=10",
"163.172.131.88:80 orport=443 id=AD253B49E303C6AB1E048B014392AC569E8A7DAE"
" ipv6=[2001:bc8:4400:2100::2:1009]:443"
" weight=10",
"178.254.44.135:80 orport=443 id=AE6A8C18E7499B586CD36246AC4BCAFFBBF93AB2"
" weight=10",
"37.187.7.74:80 orport=443 id=AEA43CB1E47BE5F8051711B2BF01683DB1568E05"
" ipv6=[2001:41d0:a:74a::1]:443"
" weight=10",
"212.129.62.232:80 orport=443 id=B143D439B72D239A419F8DCE07B8A8EB1B486FA7"
" weight=10",
"185.66.250.141:9030 orport=9001 id=B1726B94885CE3AC3910CA8B60622B97B98E2529"
" weight=10",
"193.11.114.46:9032 orport=9003 id=B83DC1558F0D34353BB992EF93AFEAFDB226A73E"
" weight=10",
Remove and blacklist 4 fallbacks which are unsuitable Remove a fallback that changed its fingerprint after it was listed This happened after to a software update: https://lists.torproject.org/pipermail/tor-relays/2016-June/009473.html Remove a fallback that changed IPv4 address Remove two fallbacks that were slow to deliver consensuses, we can't guarantee they'll be fast in future. Blacklist all these fallbacks until operators confirm they're stable.
2016-06-22 01:59:05 +02:00
/* Fallback was on 0.2.8.2-alpha list, but downloads were slow before 0.2.8.5
Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
* "178.62.36.64:9030 orport=9001 id=B87C84E38DAECFFFFDE98E5AEE5786AFDC748F2C"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"197.231.221.211:9030 orport=9001 id=BC630CBBB518BE7E9F4E09712AB0269E9DC7D626"
" weight=10",
"198.96.155.3:8080 orport=5001 id=BCEDF6C193AA687AE471B8A22EBF6BC57C2D285E"
" weight=10",
"148.251.190.229:9030 orport=9010 id=BF0FB582E37F738CD33C3651125F2772705BB8E8"
" ipv6=[2a01:4f8:211:c68::2]:9010"
" weight=10",
"188.138.112.60:1433 orport=1521 id=C414F28FD2BEC1553024299B31D4E726BEB8E788"
" weight=10",
"195.154.79.128:80 orport=443 id=C697612CA5AED06B8D829FCC6065B9287212CB2F"
" weight=10",
"37.59.46.159:9030 orport=9001 id=CBD0D1BD110EC52963082D839AC6A89D0AE243E7"
" weight=10",
"91.121.54.8:9030 orport=9001 id=CBEE0F3303C8C50462A12107CA2AE061831931BC"
" weight=10",
Add default fallback directories for the 0.2.8 alpha releases Allow fallback directories which have been stable for 30 days to work around #18050, which causes relays to submit descriptors with 0 DirPorts when restarted. (Particularly during Tor version upgrades.) Ignore low fallback directory count in alpha builds.
2016-01-18 02:34:34 +01:00
"178.62.199.226:80 orport=443 id=CBEFF7BA4A4062045133C053F2D70524D8BBE5BE"
" ipv6=[2a03:b0c0:2:d0::b7:5001]:443"
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
" weight=10",
Remove and blacklist 3 fallbacks which disappeared Blacklist them in case they appear again.
2016-06-22 04:09:32 +02:00
/* Fallback was on 0.2.8.2-alpha list, but went down before 0.2.8.5
Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
* "81.7.17.171:80 orport=443 id=CFECDDCA990E3EF7B7EC958B22441386B6B8D820"
* " ipv6=[2a02:180:1:1::517:11ab]:443"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"134.119.3.164:9030 orport=9001 id=D1B8AAA98C65F3DF7D8BB3AF881CAEB84A33D8EE"
" weight=10",
"185.13.38.75:9030 orport=9001 id=D2A1703758A0FBBA026988B92C2F88BAB59F9361"
" weight=10",
"37.187.115.157:9030 orport=9001 id=D5039E1EBFD96D9A3F9846BF99EC9F75EDDE902A"
" weight=10",
Remove 2 fallbacks: one lost guard, the other had bad uptime Leave these fallbacks in the whitelist, they may improve before 0.2.9.
2016-06-22 03:33:00 +02:00
/* Fallback was on 0.2.8.2-alpha list, but lost Guard flag before 0.2.8.5
Comment-out fallbacks in a way the stem fallback parser understands If we manually remove fallbacks in C by adding '/*' and '*/' on separate lines, stem still parses them as being present, because it only looks at the start of a line. Add a comment to this effect in the generated source code.
2016-06-23 02:49:03 +02:00
* "185.14.185.240:9030 orport=443 id=D62FB817B0288085FAC38A6DC8B36DCD85B70260"
* " weight=10",
*/
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
"37.221.162.226:9030 orport=9001 id=D64366987CB39F61AD21DBCF8142FA0577B92811"
" weight=10",
"193.35.52.53:9030 orport=9001 id=DAA39FC00B196B353C2A271459C305C429AF09E4"
" weight=10",
Add default fallback directories for the 0.2.8 alpha releases Allow fallback directories which have been stable for 30 days to work around #18050, which causes relays to submit descriptors with 0 DirPorts when restarted. (Particularly during Tor version upgrades.) Ignore low fallback directory count in alpha builds.
2016-01-18 02:34:34 +01:00
"178.62.173.203:9030 orport=9001 id=DD85503F2D1F52EF9EAD621E942298F46CD2FC10"
" ipv6=[2a03:b0c0:0:1010::a4:b001]:9001"
April 2016 fallbacks for 0.2.8-rc
2016-04-14 18:33:41 +02:00
" weight=10",
"5.34.183.205:80 orport=443 id=DDD7871C1B7FA32CB55061E08869A236E61BDDF8"
" weight=10",
"195.191.233.221:80 orport=443 id=DE134FC8E5CC4EC8A5DE66934E70AC9D70267197"
" weight=10",
"46.252.26.2:45212 orport=49991 id=E589316576A399C511A9781A73DA4545640B479D"
" weight=10",
"176.31.180.157:143 orport=22 id=E781F4EC69671B3F1864AE2753E0890351506329"
" ipv6=[2001:41d0:8:eb9d::1]:22"
" weight=10",
"131.188.40.188:443 orport=80 id=EBE718E1A49EE229071702964F8DB1F318075FF8"
" weight=10",
"91.219.236.222:80 orport=443 id=EC413181CEB1C8EDC17608BBB177CD5FD8535E99"
" weight=10",
"94.242.246.23:443 orport=9001 id=F65E0196C94DFFF48AFBF2F5F9E3E19AAE583FD0"
" ipv6=[2a01:608:ffff:ff07::1:23]:9003"
" weight=10",
"46.101.143.173:80 orport=443 id=F960DF50F0FD4075AC9B505C1D4FFC8384C490FB"
" weight=10",
"195.154.8.111:80 orport=443 id=FCB6695F8F2DC240E974510A4B3A0F2B12AB5B64"
" weight=10",
"192.187.124.98:9030 orport=9001 id=FD1871854BFC06D7B02F10742073069F0528B5CC"
" weight=10",
"193.11.164.243:9030 orport=9001 id=FFA72BD683BC2FCF988356E6BEC1E490F313FB07"
" ipv6=[2001:6b0:7:125::243]:9001"
" weight=10",
Reference in New Issue Copy Permalink