[tor-bugs] #24678 [Core Tor/Fallback Scripts]: Update fallback directory whitelist based on latest relay changes
Tor Bug Tracker & Wiki
blackhole at torproject.org
Fri Dec 22 10:25:22 UTC 2017
#24678: Update fallback directory whitelist based on latest relay changes
---------------------------------------+-----------------------------------
Reporter: teor | Owner: (none)
Type: task | Status: needs_information
Priority: Medium | Milestone: Tor:
| 0.3.3.x-final
Component: Core Tor/Fallback Scripts | Version:
Severity: Normal | Resolution:
Keywords: fallback | Actual Points: 0.2
Parent ID: #22271 | Points: 1
Reviewer: | Sponsor:
---------------------------------------+-----------------------------------
Changes (by teor):
* keywords:
fallback, 028-backport, 029-backport, 030-backport, 031-backport,
032-backport
=> fallback
* status: new => needs_information
* actualpoints: => 0.2
Comment:
I sent this email out to the operators involved.
I received one immediate bounce, I will follow up in a few days with a
tor-relays email.
{{{
Dear Relay Operator,
Your relay is on the fallback directory whitelist, and it looks like its
details
have changed. (Or, maybe I wrote them down wrong!)
Will your relay be around for the next two years?
Will its IP, ports, and fingerprint stay the same?
Please reply to this email and let us know!
Thanks
Tim
Here is the full list:
Changed fingerprint:
Has OR 163.172.138.22:443 / [2001:bc8:4400:2100::1:3]:443 changed
fingerprint from 8664DC892540F3C789DB37008236C096C871734D to
16102E458460349EE45C0901DAA6C30094A9BBEA?
163.172.138.22:80 orport=443 id=16102E458460349EE45C0901DAA6C30094A9BBEA
ipv6=[2001:bc8:4400:2100::1:3]:443 # mkultra
Changed IPv4:
Has 32E7AAF1F602814D699BEF6761AD03E387758D49 changed IPv4 from
212.51.156.193 to 212.51.156.17?
212.51.156.17:995 orport=110 id=32E7AAF1F602814D699BEF6761AD03E387758D49
ipv6=[2a02:168:4a01::49]:110 # Cortez
Has F10BDE279AE71515DDCCCC61DC19AC8765F8A3CC changed IPv4 from
192.99.212.139 to 193.70.112.165?
193.70.112.165:80 orport=443 id=F10BDE279AE71515DDCCCC61DC19AC8765F8A3CC #
ParkBenchInd001
Changed DirPort:
Has 7350AB9ED7568F22745198359373C04AC783C37C changed DirPort from
176.31.191.26:80 to 176.31.191.26:110?
176.31.191.26:110 orport=995 id=7350AB9ED7568F22745198359373C04AC783C37C #
Casper03
Has EBE718E1A49EE229071702964F8DB1F318075FF8 changed DirPort from
131.188.40.188:443 to 131.188.40.188:1443?
131.188.40.188:1443 orport=80 id=EBE718E1A49EE229071702964F8DB1F318075FF8
ipv6=[2001:638:a000:4140::ffff:188]:80 # fluxe4
Has F4263275CF54A6836EE7BD527B1328836A6F06E1 changed DirPort from
37.187.102.108:9090 to 37.187.102.108:80?
37.187.102.108:80 orport=443 id=F4263275CF54A6836EE7BD527B1328836A6F06E1
ipv6=[2001:41d0:a:266c::1]:443 # EvilMoe
Changed IPv6 ORPort:
Has 774555642FDC1E1D4FDF2E0C31B7CA9501C5C9C7 changed IPv6 ORPort from
[2a03:b0c0:2:d0::5:f001]:9001 to [2a03:b0c0:2:d0::26c0:1]:9001?
188.166.133.133:9030 orport=9001
id=774555642FDC1E1D4FDF2E0C31B7CA9501C5C9C7
ipv6=[2a03:b0c0:2:d0::26c0:1]:9001 # dropsy
Gained IPv6 address:
Has AD19490C7DBB26D3A68EFC824F67E69B0A96E601 gained an IPv6 address
[2a01:4f8:221:1ac1:dead:beef:7005:9001]:9001?
188.40.128.246:9030 orport=9001
id=AD19490C7DBB26D3A68EFC824F67E69B0A96E601
ipv6=[2a01:4f8:221:1ac1:dead:beef:7005:9001]:9001 # sputnik
Has B0553175AADB0501E5A61FC61CEA3970BE130FF2 gained an IPv6 address
[2a01:4f8:190:30e1::2]:9001?
5.9.147.226:9030 orport=9001 id=B0553175AADB0501E5A61FC61CEA3970BE130FF2
ipv6=[2a01:4f8:190:30e1::2]:9001 # zwiubel
Has FE296180018833AF03A8EACD5894A614623D3F76 gained an IPv6 address
[2607:5300:201:3000::17d3]:9002?
149.56.45.200:9030 orport=9001 id=FE296180018833AF03A8EACD5894A614623D3F76
ipv6=[2607:5300:201:3000::17d3]:9002 # PiotrTorpotkinOne
}}}
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/24678#comment:2>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list