Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C censorship-analysis
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Service Desk
    • Milestones
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Anti-censorship
  • censorship-analysis
  • Issues
  • #32026
Closed
Open
Created Oct 10, 2019 by Trac@tracbot

Using An Alternative To TCP To Avoid Packet Injection?

According to https://www.cs.tufts.edu/comp/116/archive/fall2016/ctang.pdf , the GFW only injects packets, mostly TCP RST signals. What if TOR has bridges/servers that do not respond to TCP RST? This would render the connection interfering part of GFW useless. Here, a connection ends only when both sides send a "END" signal to the other side with their private key for the connection only that is shared through the connection. We don't even need to obfuscate TOR traffic anymore as the packets are not blocked. With the DNS inspection, we could have IPs for bridges/servers, which do the DNS queries on non censored DNS servers.

Trac:
Username: Aphrodites1995

Assignee
Assign to
Time tracking