[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #28877 [Core Tor/Tor]: 'GETINFO desc/fingerprints' command to get known relays
#28877: 'GETINFO desc/fingerprints' command to get known relays
--------------------------+----------------------------------
Reporter: wagon | Owner: (none)
Type: enhancement | Status: assigned
Priority: Medium | Milestone: Tor: unspecified
Component: Core Tor/Tor | Version:
Severity: Normal | Resolution:
Keywords: | Actual Points:
Parent ID: | Points: 2
Reviewer: | Sponsor:
--------------------------+----------------------------------
Changes (by teor):
* points: => 2
* type: defect => enhancement
* milestone: => Tor: unspecified
Comment:
Replying to [comment:9 atagar]:
> I need the ability to iterate over all descriptors without getting such
a large response. That said, I just thought of a cheap option that's far
simpler than pagination: **add a 'GETINFO desc/fingerprints' method that
provides the all server descirptor fingerprints tor knows about**.
>
> I can call that to get an enumeration of the relays tor has descriptors
for, then query them one at a time to break up our fourteen megabyte
response. I suspect we'd want separate methods for other descriptor types
('GETINFO md/fingerprints' and 'GETINFO ns/fingerprints') because the
relays we have information for are not necessarily the same between
document types.
Here's a simple, generic scheme that we could implement:
If `path/to/*` takes a key, then `path/to` returns a list of known keys.
For example:
`GETINFO desc/id/<OR identity>` is an existing command.
We add `GETINFO desc/id`, which returns a list of known `<OR identity>`
for `GETINFO desc/id/<OR identity>`.
Controllers should be prepared to handle keys that disappear before they
are queried, for example, due to a consensus update.
This code should be relatively easy to implement in Tor.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28877#comment:10>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs