Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S Snowflake
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 93
    • Issues 93
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • Pluggable Transports
  • Snowflake
  • Issues
  • #40014
Closed
Open
Issue created Oct 14, 2020 by Cecylia Bocovich@cohoshOwner

Make Snowflake's DTLS fingerprint more similar to popular WebRTC implementations

Some recent work by researchers at Princeton shows that Snowflake's DTLS fingerprint differs from some other popular WebRTC implementations (Facebook, Google, and Discord): https://arxiv.org/pdf/2008.03254.pdf

I'm hesitant to rush changes to the fingerprint without a more complete comparison to more WebRTC implementations popular in censored regions. But, we can get a start on figuring out how to change the fingerprint in pion and see whether we will need to submit upstream patches to provide us with this kind of agility. Something like uTLS would be great for us in the long run.

Assignee
Assign to
Time tracking