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

Re: [tor-bugs] #7902 [Tor]: connection_ap_process_end_not_open() does not handle END_STREAM_REASON_DONE correctly

#7902: connection_ap_process_end_not_open() does not handle END_STREAM_REASON_DONE
correctly
-----------------------+----------------------------------------------------
    Reporter:  asn     |       Owner:                    
        Type:  defect  |      Status:  closed            
    Priority:  normal  |   Milestone:  Tor: 0.2.4.x-final
   Component:  Tor     |     Version:                    
  Resolution:  fixed   |    Keywords:  tor-client        
      Parent:          |      Points:                    
Actualpoints:          |  
-----------------------+----------------------------------------------------

Comment(by mikeperry):

 Hrm.. If the only case where we can get a END_STREAM_REASON_DONE in
 connection_ap_handshake_socks_reply() is something that shouldn't happen,
 maybe I should just leave the path bias state as-is so we can probe the
 circuit upon teardown. I found quite a few cases where tagging could
 induce codepaths that shouldn't happen while looking at what sorts of
 reason codes come back..

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