Opened 4 years ago

Closed 4 years ago

#8253 closed enhancement (implemented)

Parse microdescriptors

Reported by: atagar Owned by: atagar
Priority: High Milestone:
Component: Core Tor/Stem Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: #8252 Points:
Reviewer: Sponsor:

Description

We presently lack the ability to parse tor microdescriptors. This is not needed to reach feature parity with metrics-lib (Karsten said on #7987 that they aren't relevant to metrics), but it would still be a nice capability to have.

Child Tickets

Change History (3)

comment:1 Changed 4 years ago by atagar

  • Resolution set to worksforme
  • Status changed from new to closed

Oops, I think that I was confused about this. We *do* support microdescriptor consensuses - for some reason I thought there was another microdescriptor documents we were missing. From a look over the dir-spec guess I was wrong - resolving.

comment:2 Changed 4 years ago by atagar

  • Priority changed from minor to major
  • Resolution worksforme deleted
  • Status changed from closed to reopened

Grrr, I was wrong about being wrong. We parse microdescriptor flavored network status documents but not the microdescriptors themselves. Reopening and merging with #8320. This has just supplanted tutorials at the top of my todo list since server descriptors are no longer fetched by default.

Also filed #8323 since the controller interface is lacking a method of fetching all microdescriptors (I'll likely need to hack around this by reading 'em from disk).

comment:3 Changed 4 years ago by atagar

  • Resolution set to implemented
  • Status changed from reopened to closed

Done and pushed...

https://gitweb.torproject.org/stem.git/commitdiff/23d2332b2514fd9194e64cb1859614014087394b

We still need to add support to the controller. I'll tackle that next, but we now have parsing support so resolving this ticket.

Note: See TracTickets for help on using tickets.