Changes between Initial Version and Version 5 of Ticket #26122


Ignore:
Timestamp:
May 17, 2018, 7:29:25 PM (11 months ago)
Author:
dcf
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #26122

    • Property Status changed from new to closed
    • Property Type changed from defect to enhancement
    • Property Component changed from Obfuscation/Censorship analysis to Obfuscation/Obfsproxy
    • Property Summary changed from obfs4proxy: closeAfterDelay() should to conform to obfs4 spec to obfs4: remove byte threshold for disconnection
    • Property Resolution changed from to wontfix
  • Ticket #26122 – Description

    initial v5  
    1 obfs4-spec.txt:
    2 > 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.
     1As 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.
    32
    4 closeAfterDelay() can to violate spec by closing connection immediately.
     3Original description:
     4> obfs4-spec.txt:
     5> > 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.
     6>
     7> closeAfterDelay() can to violate spec by closing connection immediately.