Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #26122
Closed
Open
Issue created May 17, 2018 by cypherpunks@cypherpunks

obfs4: remove byte threshold for disconnection

As currently implemented, an obfs4 server disconnects an unauthenticated client after 8192–16383 received bytes or 30–90 seconds. (The exact values are chosen randomly from these ranges for each server.) The patch in comment:1 proposes to remove the byte threshold and keep the time threshold, as a mitigation against active-probing distinguishers such as the one in #26083 (moved).

Original description:

obfs4-spec.txt:

On the event of a failure at this point implementations SHOULD delay dropping the TCP connection from the client by a random interval to make active probing more difficult.

closeAfterDelay() can to violate spec by closing connection immediately.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking