Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#1754 closed task (implemented)

Microdescriptors: caches fetch and server all flavors of consensus

Reported by: nickm Owned by: nickm
Priority: Medium Milestone: Deliverable-Sep2010
Component: Core Tor/Tor Version:
Severity: Keywords: tor-relay
Cc: Actual Points:
Parent ID: #1748 Points:
Reviewer: Sponsor:


Right now, caches only know how to download and use one single consensus flavor. We need them to be able to fetch, parse, store, and serve every flavor. Right now, that means "normal" and "microdesc".

Storing and serving are already implemented (I believe) since authorities do them. Parsing and fetching remain are partially implemented in my "microdesc_dl" branch.

See proposals 158 and 162 for more information.

Child Tickets

Change History (5)

comment:1 Changed 10 years ago by nickm

A fun note: caches use consensuses for up to three things:

  • Serving them to non-caches
  • Learning which descriptors (and microdescriptors) to download.
  • Using them to learn which servers exist, so they can build circuits themselves.

The first one can be done without parsing the consensus; just check its signature. The second means that all caches need both consensuses, parsed.

comment:2 Changed 10 years ago by nickm

This is currently done in my microdesc_dl_v2 branch.

comment:3 Changed 10 years ago by nickm

Resolution: implemented
Status: newclosed

Merged into master.

comment:4 Changed 8 years ago by nickm

Keywords: tor-relay added

comment:5 Changed 8 years ago by nickm

Component: Tor RelayTor
Note: See TracTickets for help on using tickets.