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

Re: [tor-bugs] #34042 [Circumvention/Snowflake]: Reduce DataChannelTimeout

#34042: Reduce DataChannelTimeout
-------------------------------------+------------------------
 Reporter:  dcf                      |          Owner:  (none)
     Type:  enhancement              |         Status:  new
 Priority:  Medium                   |      Milestone:
Component:  Circumvention/Snowflake  |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:                           |  Actual Points:
Parent ID:                           |         Points:
 Reviewer:                           |        Sponsor:
-------------------------------------+------------------------

Comment (by cohosh):

 I just realized that we can't use the datachannel timeout to detect non-
 working proxies on the client-side the same way we do on the proxy side.
 The client initiates the datachannel, so once they set the remote
 description, they will call `datachannel.OnOpen` regardless of whether or
 not the proxy is reachable. So I'm not actually sure what the utility of
 this timeout is on the client side.

 We could change it to be the time from when datachannel.OnOpen is called
 and when we receive the first incoming byte from the proxy?

 I guess we still need to block on the datachannel opening before we can
 (attempt to) send data to it, so we'll still want a timeout here. We
 should just be aware that this timeout isn't telling us the same thing the
 datachannel timeout at the proxy is.

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