[tor-bugs] #10882 [Globe]: New server-side Globe should attempt to run full fingerprints through SHA-1 on client side if possible

[Tor Bug Tracker & Wiki]

#10882: New server-side Globe should attempt to run full fingerprints through SHA-1
on client side if possible
-----------------------------+------------------
     Reporter:  karsten      |      Owner:  rndm
         Type:  enhancement  |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  Globe        |    Version:
   Resolution:               |   Keywords:
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+------------------

Comment (by karsten):

 The Globe server, if asked for "search2=<str>", simply forwards the
 request to the Onionoo server.  Nothing to worry about here, Onionoo will
 handle the case of <hash> being a SHA-1 fingerprint (if the user put in
 their original fingerprint) or the SHA-1 of the SHA-1 fingerprint (if the
 user put in a fingerprint hash).

 If the Globe server is asked for "search=<str>", it performs the same
 check as the JavaScript Globe would have done.  If it detects 40 hex
 chars, it computes the SHA-1 and sends it to Onionooo.  Otherwise it
 simply forwards to Onionoo.  When Onionoo replies, Globe server checks if
 the response contains a single bridge with the hashed fingerprint being
 the SHA-1 that Globe server computed.  In this case the <str> part that it
 was given was a non-hashed fingerprint.  If so, Globe server includes a
 warning that users shouldn't put in their original fingerprint and
 suggests to use the fingerprint hash instead in the future.

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