[tor-bugs] #28942 [Circumvention/Snowflake]: Evaluate pion WebRTC
Tor Bug Tracker & Wiki
blackhole at torproject.org
Wed Jun 19 19:32:31 UTC 2019
#28942: Evaluate pion WebRTC
-------------------------------------+-------------------------------
Reporter: backkem | Owner: cohosh
Type: enhancement | Status: assigned
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 dcf):
Replying to [comment:17 cmm323]:
> Great! One concern I have is that if there are specific features in
`pion` implementation that are different from the native implementation,
which make it easy to block.
I am not too worried about that at this point, because what little
research we did using libwebrtc ([[doc/Snowflake/Fingerprinting]]) showed
that even with the native library, Snowflake did not match other
applications. I don't think swapping one library for another costs much at
this point, in that respect.
Replying to [comment:18 Sean-Der]:
> We *should* have zero differences
I would be surprised if this is the case--unless pion has paid
extraordinary attention to matching externally visible protocol
implementation details, which goes farther than interoperability. What
about the order of ciphersuites in the DTLS handshake, or the metadata
inside STUN messages? One of the things we found is that there's no single
"WebRTC" fingerprint, nor even a single "Chrome WebRTC" fingerprint--it
depends on the specific application. That said, I'm glad that you are
involved, and I am hopeful that pion will be easier to adapt if and when
needed.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28942#comment:19>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
More information about the tor-bugs
mailing list