Disorder strategy from byeDPI #323
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
fortuna
requested changes
Nov 12, 2024
|
Made changes to address comments, thanks! |
fortuna
requested changes
Nov 12, 2024
x/configurl/doc.go
Outdated
| # Examples | ||
|
|
||
| Packet splitting - To split outgoing streams on bytes 2 and 123, you can use: | ||
|
|
||
| split:2|split:123 | ||
|
|
||
| Disorder transport - Send some of the packets out of order |
There was a problem hiding this comment.
Suggested change
| Disorder transport - Send some of the packets out of order | |
| Disorder transport - Send some of the packets out of order: |
x/configurl/doc.go
Outdated
|
|
||
| disorder:0|split:123 | ||
|
|
||
| Split at position 123, then send packet 0 of 123 bytes (from splitting) out of order. The network filter will first receive packet 1, only then packet 0. |
There was a problem hiding this comment.
Suggested change
| Split at position 123, then send packet 0 of 123 bytes (from splitting) out of order. The network filter will first receive packet 1, only then packet 0. | |
| Split at position 123, then send packet 0 of 123 bytes (from splitting) out of order. The network filter will first receive packet 1, only then packet 0. This is done by setting the hop limit for the write to 1, and then restoring it. It will be sent with its original hop limit on retransmission. |
PeterZhizhin
force-pushed
the
disorder
branch
from
2d98f62 to
b6aef3d
Compare
fortuna
approved these changes
Nov 13, 2024
fortuna
reviewed
Nov 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Allows to send TCP packets out of order
This is achieved by sending some packets with TTL=1, and then setting TTL back to normal.
Tested with the following command:
This splits the TCP request at position 123, at SNI record:
meduis in packet 0,za.iois in packet 1.The network filters will receive a packet containing
za.iofirst, then another packet withmedu.The receiver will then reassemble the packets in it's TCP stack.
Can be combined with
tlsfragas well like this: