Re: [tor-bugs] #11480 [Tor]: Implement the single guard node proposal

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#11480: Implement the single guard node proposal
------------------------+--------------------------------
     Reporter:  asn     |      Owner:
         Type:  task    |     Status:  new
     Priority:  normal  |  Milestone:  Tor: 0.2.6.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-client
Actual Points:          |  Parent ID:
       Points:          |
------------------------+--------------------------------

Comment (by asn):

 Replying to [comment:3 asn]:
 >
 > == Prioritize young guards for non-guard tasks ==
 > * Implementation plan:
 >   Download/parse/verify old consensuses in an external script,
 >   write file with results,
 >   have little-t-tor read the results.
 >

 Two questions on this task (also see #10968):

 a) How are we going to get past consesuses? AFAIK, directories don't keep
 and serve old consesuses. Is metrics.tpo the only place where we can get
 them? Is it reasonalbe to make metrics.tpo a single point of failure for
 this feature?

 b) We will need to verify the sigs of the past consesuses. Can arm verify
 signatures of Tor documents? Also, what can go wrong with verifying
 consesus sigs from many months ago? Have auths ever changed their identity
 keys? Also, what happens if we try to parse a badly-signed consesus?
 Should we just ignore it?

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11480#comment:4>
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