Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #32026

Closed (moved)
Open
Opened 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

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#32026