Opened 3 years ago

Closed 3 years ago

Last modified 2 years ago

#24678 closed task (implemented)

Update fallback directory whitelist based on latest relay changes

Reported by: teor Owned by: teor
Priority: Medium Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Fallback Scripts Version:
Severity: Normal Keywords: fallback, review-group-29
Cc: Actual Points: 0.5
Parent ID: Points: 1
Reviewer: Sponsor:


We need to run the script, and get the list of warnings about changed relay details.

Then we can contact each operator to see if the change is permanent.

Child Tickets

Change History (10)

comment:1 Changed 3 years ago by teor

Type: defecttask

comment:2 Changed 3 years ago by teor

Actual Points: 0.2
Keywords: 028-backport 029-backport 030-backport 031-backport 032-backport removed
Status: newneeds_information

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!



Here is the full list:

Changed fingerprint:

Has OR / [2001:bc8:4400:2100::1:3]:443 changed fingerprint from 8664DC892540F3C789DB37008236C096C871734D to 16102E458460349EE45C0901DAA6C30094A9BBEA? orport=443 id=16102E458460349EE45C0901DAA6C30094A9BBEA ipv6=[2001:bc8:4400:2100::1:3]:443 # mkultra

Changed IPv4:

Has 32E7AAF1F602814D699BEF6761AD03E387758D49 changed IPv4 from to orport=110 id=32E7AAF1F602814D699BEF6761AD03E387758D49 ipv6=[2a02:168:4a01::49]:110 # Cortez

Has F10BDE279AE71515DDCCCC61DC19AC8765F8A3CC changed IPv4 from to orport=443 id=F10BDE279AE71515DDCCCC61DC19AC8765F8A3CC # ParkBenchInd001

Changed DirPort:

Has 7350AB9ED7568F22745198359373C04AC783C37C changed DirPort from to orport=995 id=7350AB9ED7568F22745198359373C04AC783C37C # Casper03

Has EBE718E1A49EE229071702964F8DB1F318075FF8 changed DirPort from to orport=80 id=EBE718E1A49EE229071702964F8DB1F318075FF8 ipv6=[2001:638:a000:4140::ffff:188]:80 # fluxe4

Has F4263275CF54A6836EE7BD527B1328836A6F06E1 changed DirPort from to 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? 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? 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? orport=9001 id=B0553175AADB0501E5A61FC61CEA3970BE130FF2 ipv6=[2a01:4f8:190:30e1::2]:9001 # zwiubel

Has FE296180018833AF03A8EACD5894A614623D3F76 gained an IPv6 address [2607:5300:201:3000::17d3]:9002? orport=9001 id=FE296180018833AF03A8EACD5894A614623D3F76 ipv6=[2607:5300:201:3000::17d3]:9002 # PiotrTorpotkinOne

comment:3 Changed 3 years ago by teor

Owner: set to teor
Status: needs_informationassigned

comment:4 Changed 3 years ago by teor

Status: assignedneeds_information

comment:5 Changed 3 years ago by teor

Ok, one last shot before we just assume they are permanent, and update all the entries:

comment:6 Changed 3 years ago by teor

Still awaiting responses from these operators:

ParkBenchInd001 - F10BDE279AE71515DDCCCC61DC19AC8765F8A3CC
sputnik - AD19490C7DBB26D3A68EFC824F67E69B0A96E601
zwiubel - B0553175AADB0501E5A61FC61CEA3970BE130FF2

comment:7 Changed 3 years ago by teor

Actual Points: 0.20.5
Parent ID: #22271#22321
Status: needs_informationneeds_review

Two of these fallbacks added IPv6 addresses, and one changed IPv4.

I have assumed these changes are permanent, and updated them in the whitelist in my fallback_whiteblack_changes branch at

This can close when #22321 closes.

comment:8 Changed 3 years ago by nickm

Keywords: review-group-29 added

comment:9 Changed 3 years ago by nickm

Parent ID: #22321
Resolution: implemented
Status: needs_reviewclosed

The parent is closed; I'm presuming this can close too.

comment:10 Changed 2 years ago by teor

Cc: teor@… removed

Remove useless Cc

Note: See TracTickets for help on using tickets.