adding long padding fuzzing strategy and a randomized flag for https #1
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Hi,
I'm proposing to add a "long padding" fuzzing strategy for the HTTP and HTTPS hostname/servername fields that generates paddings up to the maximum field size buffer of 255 characters.
I've also added a new "randomized" flag which provides the option to use the uTLS client HelloRandomized clientHelloID option instead of the HelloGolang option. This modifies the overall structure of the client hello message by rearranging or nesting fields differently and may help uncover vulnerabilities related to parsing and processing of TLS messages.
Best regards,
Thomas