Opened 5 years ago

Closed 4 years ago

Last modified 2 years ago

#11103 closed enhancement (wontfix)

Get rid of the v2dir status flag now that v2 dir protocol is dead?

Reported by: arma Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Is it still used for anything? The rest of the v2 dir protocol is gone now.

(Maybe when we finish this one, we also close #1338.)

Child Tickets

Change History (4)

comment:1 Changed 5 years ago by nickm

Milestone: Tor: 0.2.6.x-finalTor: 0.2.???

0.2.4 clients and earlier still parse it; 0.2.4 uses it in two places in routerlist.c that I can't be sure are completely irrelevant. In particular, when we fetch v2 dirinfo in order to cache it, we look for a v2dir flag. Will removing v2dir from all the nodes be safe? Who can say?

I recommend that we remove the V2Dir flag from consensuses once 0.2.4 is unsupported. After compression, it costs us practically nothing:

[1344]$ cat ~/.tor/cached-microdesc-consensus |gzip -9 -c |wc -c
451574
[1345]$ cat ~/.tor/cached-microdesc-consensus |perl -pe 's/ V2Dir//;' |gzip -9 -c |wc -c
450332

comment:2 Changed 4 years ago by nickm

Resolution: wontfix
Status: newclosed

Note that #12538 would supersede this.

comment:3 Changed 3 years ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:4 Changed 2 years ago by nickm

Milestone: Tor: 0.3.???

Milestone deleted

Note: See TracTickets for help on using tickets.