[tor-bugs] #13135 [Onionoo]: Support various fingerprint formats

[Tor Bug Tracker & Wiki]

#13135: Support various fingerprint formats
-----------------------------+-----------------
     Reporter:  Sebastian    |      Owner:
         Type:  enhancement  |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  Onionoo      |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+-----------------

Comment (by karsten):

 Suggested changes:

  1. The `search` parameter supports searching by (beginning of)
 base64-encoded relay fingerprint.  This needs input from Onionoo client
 developers for escaping `+` and `/`.  Technically, this constitutes a
 major protocol change that requires at least one month notice before
 deployment to give client developers the chance to implement filters if
 their searches are not supposed to return matching base64-encoded
 fingerprints.

  2. (This is actually a suggestion to not change anything in Onionoo:)
 Regarding listing base64-encoded fingerprint, I'm considering not to add a
 field for that but asking client developers to re-encode the hex
 fingerprint if they want to display the base64-encoded one.  Let's save
 bandwidth by avoiding to transmit redundant data.  Unless binary encoding
 is something that clients cannot or shouldn't be required to do?

  3. `details` documents contain new fields `server_digest` and
 `extra_digest` with hex representations of server descriptor and extra-
 info descriptor digests.  This is a minor protocol change that I can
 implement in the next day or two and deploy by the end of the week if we
 agree it's a good idea.  Atlas and friends can then display the new fields
 if they wish to.  They could even include links to the descriptors as
 served by gabelmoo, if you want to.

  4. `details` documents contain a new field `micro_digest` with the
 microdescriptor digest encoded in base64 with trailing =s omitted.  This
 requires parsing microdesc consensuses which we're currently not doing, so
 we should run some performance tests before deploying this on the server.
 Don't expect this feature this month, I'd say.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13135#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online