[tor-bugs] #28942 [Circumvention/Snowflake]: Evaluate pion WebRTC

Tor Bug Tracker & Wiki blackhole at torproject.org
Tue Jun 25 19:33:36 UTC 2019


#28942: Evaluate pion WebRTC
-------------------------------------+-------------------------------
 Reporter:  backkem                  |          Owner:  cohosh
     Type:  enhancement              |         Status:  accepted
 Priority:  Medium                   |      Milestone:
Component:  Circumvention/Snowflake  |        Version:
 Severity:  Normal                   |     Resolution:
 Keywords:  ex-sponsor-19            |  Actual Points:
Parent ID:                           |         Points:
 Reviewer:                           |        Sponsor:  Sponsor28-can
-------------------------------------+-------------------------------

Comment (by cohosh):

 Replying to [comment:25 backkem]:
 > - As mentioned in the original ticket and the SCTP PR, you can 'detach'
 a data channel to get access to the underlying idiomatic API based on the
 io.ReadWriteCloser.
 Thanks! I replied there but I'm copying the answer here to keep everyone
 in the same loop. While this does solve the problem of how to handle an
 `io.ErrShortBuffer`, it doesn't fix the bug in SCTP. I think we'd still
 prefer to have access to the `OnMessage` callback anyway instead of
 implementing our own readLoop, but depending on how you decide to handle
 the `io.ErrShortBuffer` return in your readLoop we may need to go that
 route.
 > - There are good discussions about alternative signaling/rendezvous
 strategies in https://github.com/libp2p/specs/pull/159 and
 https://github.com/libp2p/go-libp2p-webrtc-direct/issues/14 that may be of
 interest.
 Thanks! This is really interesting, we'll take a look. We have a few
 tickets about alternative signaling as well: #25985 and #25985

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


More information about the tor-bugs mailing list