Yawning Angel 1a6129b66f obfs4: Alter tear down behavior to be less distinctive ... The old behavior closed the connection on handshake failure after: * The first N bytes (random on a per-server basis). * The first M seconds (random on a per-server basis). Whichever came first. As Sergey Frolov kindly points out, depending on which conditions cause termination, the server will send either a FIN or a RST. This change will remove the "amount read" based termination threshold, so that connections that cause failed handshakes will discard all data received until the teardown time is reached. Thanks to Sergey Frolov for bringing this issue to my attention.		2019-06-21 00:02:37 +00:00
..
base	Update my e-mail address (no functional changes)	2019-05-20 04:53:24 +00:00
meeklite	Update my e-mail address (no functional changes)	2019-05-20 04:53:24 +00:00
obfs2	Update my e-mail address (no functional changes)	2019-05-20 04:53:24 +00:00
obfs3	Update my e-mail address (no functional changes)	2019-05-20 04:53:24 +00:00
obfs4	obfs4: Alter tear down behavior to be less distinctive	2019-06-21 00:02:37 +00:00
scramblesuit	Update my e-mail address (no functional changes)	2019-05-20 04:53:24 +00:00
transports.go	Update my e-mail address (no functional changes)	2019-05-20 04:53:24 +00:00