Opened 4 months ago

Last modified 6 days ago

#28794 needs_revision task

Run an opt-in process for relay operators to become fallbacks in 2019

Reported by: teor Owned by: phoul
Priority: Medium Milestone:
Component: Core Tor/Fallback Scripts Version:
Severity: Normal Keywords: fallback
Cc: teor Actual Points:
Parent ID: #28793 Points:
Reviewer: Sponsor:

Description (last modified by teor)

Mail tor-relays and asking if stable relay operators want to become fallbacks. Then update fallback whitelist based on the opt-ins.

Child Tickets

Change History (15)

comment:1 Changed 4 months ago by teor

Description: modified (diff)

comment:2 Changed 4 months ago by teor

Description: modified (diff)

comment:3 Changed 4 months ago by teor

Type: defecttask

comment:4 Changed 4 months ago by teor

An operator asked us to remove these whitelist entries:

~/tor/scripts/maint $ grep 5.9.158.75  fallback.whitelist
5.9.158.75:80 orport=443 id=1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA ipv6=[2a01:4f8:190:514a::2]:443
5.9.158.75:9030 orport=9001 id=D11D11877769B9E617537B4B46BFB92B443DE33D ipv6=[2a01:4f8:190:514a::2]:9001

comment:5 Changed 4 months ago by teor

An operator has changed the keys and IP address on this relay, and wants the new relay with the same name added to the whitelist:

41C59606AFE1D1AA6EC6EF6719690B856F0B6587
178.17.170.156
TorExitMoldova2

comment:6 Changed 4 months ago by teor

An operator asked us to remove this fallback:

B6904ADD4C0D10CDA7179E051962350A69A63243 at 81.2.209.10

https://lists.torproject.org/pipermail/tor-relays/2018-December/016792.html

comment:7 in reply to:  4 Changed 3 months ago by toralf

Replying to teor:

An operator asked us to remove these whitelist entries:

~/tor/scripts/maint $ grep 5.9.158.75  fallback.whitelist
5.9.158.75:80 orport=443 id=1AF72E8906E6C49481A791A6F8F84F8DFEBBB2BA ipv6=[2a01:4f8:190:514a::2]:443
5.9.158.75:9030 orport=9001 id=D11D11877769B9E617537B4B46BFB92B443DE33D ipv6=[2a01:4f8:190:514a::2]:9001

(due to new hardware and switching to offline key handling). And BTW I prefer to replace them with these

5.9.158.75:80 orport=443 id=63BF46A63F9C21FD315CD061B3EAA3EB05283A0A ipv6=[2a01:4f8:190:514a::2]:443
5.9.158.75:9030 orport=9001 id=509EAB4C5D10C9A9A24B4EA0CE402C047A2D64E6 ipv6=[2a01:4f8:190:514a::2]:9001

comment:8 Changed 3 months ago by phoul

I have created a new branch to track these changes: https://github.com/Phoul/tor/tree/28793, and the current changes were applied at https://github.com/Phoul/tor/commit/db748bc951f3095ea299f8ca5f7d2a4d9c108490.

comment:9 Changed 3 months ago by phoul

A user submitted the following relay fingerprints for inclusion:

D379A1CB8285748FFF64AE94296CA89878F25B22
9288B75B5FF8861EFF32A6BE8825CC38A4F9F8C2
EE4AF632058F0734C1426B1AD689F47445CA2056
B57A87009FA838471FB2227DDE68165AB2A2FCC4
465D17C6FC297E3857B5C6F152006A1E212944EA
7AAF5597B18D82CC90CA95FB7976A1CEA4A32E06
39F91959416763AFD34DBEEC05474411B964B2DC
4DC4E6187F1193F2717A5E3DF5ACEBD6B162D5CC
57C6DF5B93E54EB9C8DB90029D9E9A1111BD34D2
3B07C500AC17E7B5A1EE616613E104A094AB87F3
8F6197E5508338B3E3A6BFF59F9EC8F21E1375FB
79E683340B80676DCEB029E48FBD36BC66EBDA1E
A86EC24F5B8B964F67AC7C27CE92842025983274
A9DB853547A6459AB5190E62BF2F7B8F068FEB0A

https://lists.torproject.org/pipermail/tor-relays/2019-January/016848.html

comment:10 in reply to:  9 Changed 3 months ago by phoul

Replying to phoul:

A user submitted the following relay fingerprints for inclusion:

D379A1CB8285748FFF64AE94296CA89878F25B22
9288B75B5FF8861EFF32A6BE8825CC38A4F9F8C2
EE4AF632058F0734C1426B1AD689F47445CA2056
B57A87009FA838471FB2227DDE68165AB2A2FCC4
465D17C6FC297E3857B5C6F152006A1E212944EA
7AAF5597B18D82CC90CA95FB7976A1CEA4A32E06
39F91959416763AFD34DBEEC05474411B964B2DC
4DC4E6187F1193F2717A5E3DF5ACEBD6B162D5CC
57C6DF5B93E54EB9C8DB90029D9E9A1111BD34D2
3B07C500AC17E7B5A1EE616613E104A094AB87F3
8F6197E5508338B3E3A6BFF59F9EC8F21E1375FB
79E683340B80676DCEB029E48FBD36BC66EBDA1E
A86EC24F5B8B964F67AC7C27CE92842025983274
A9DB853547A6459AB5190E62BF2F7B8F068FEB0A

https://lists.torproject.org/pipermail/tor-relays/2019-January/016848.html

These have been added at https://github.com/Phoul/tor/commit/fa519b85502a1264ff02785a69b4c4d2cd7cab55

comment:11 Changed 3 months ago by teor

Hi Phoul,

In #27914, we split the fallback scripts out into https://git.torproject.org/fallback-scripts.git . We're still working on syncing it with https://github.com/torproject/fallback-scripts.git (#29101). After #29101 closes, can you move your changes to fallback-scripts?

Thanks!

comment:12 Changed 3 months ago by teor

Milestone: Tor: unspecified

After #27914, fallback-scripts is its own repository. Fallback changes are no longer tied to Tor releases.

comment:13 Changed 3 months ago by teor

fallback directory mirror armbrust: E781F4EC69671B3F1864AE2753E0890351506329 is going down soon. It should be removed from the whitelist.

https://lists.torproject.org/pipermail/tor-relays/2019-January/016878.html

comment:14 in reply to:  13 Changed 7 weeks ago by phoul

Replying to teor:

fallback directory mirror armbrust: E781F4EC69671B3F1864AE2753E0890351506329 is going down soon. It should be removed from the whitelist.

https://lists.torproject.org/pipermail/tor-relays/2019-January/016878.html

The list has now been migrated to the fallback-scripts repo, and this change has been made at https://github.com/Phoul/fallback-scripts/commit/30dc6bd347860a3df42f6c205550f2f0766e2151

comment:15 Changed 6 days ago by teor

Status: assignedneeds_revision

An operator emailed me and asked me to remove this relay from the whitelist:
https://metrics.torproject.org/rs.html#details/36B9E7AC1E36B62A9D6F330ABEB6012BA7F0D400

Note: See TracTickets for help on using tickets.