[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #11648 [Tor]: Problem parsing .z-compressed descriptors fetched via DirPort



#11648: Problem parsing .z-compressed descriptors fetched via DirPort
-------------------------+-----------------------
     Reporter:  karsten  |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:
    Component:  Tor      |    Version:
   Resolution:           |   Keywords:  tor-relay
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-----------------------

Comment (by wfn):

 turtles seems to consistently produce a bogus `all.z` (which at this point
 can be identified by the trailing `0000ffff`, which seems to be the way a
 `Z_SYNC_FLUSH` (not `Z_FINISH`) ends.)) Other authorities inconclusive,
 but IAC turtles seems to be unique in its failure rate (subsequent
 requests do not help.)

 I wonder what can its last entry in the `conn->fingerprint_stack` (when it
 (well, `dir_fps`) gets filled) be? Can we infer, etc.? ''Can'' there be a
 tangling node on `conn->fingerprint_stack` which fails at descriptor
 lookup?

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