Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TLS Renegotiation Support #13

Open
dkx-daniel opened this issue Aug 2, 2024 · 0 comments · May be fixed by #14
Open

TLS Renegotiation Support #13

dkx-daniel opened this issue Aug 2, 2024 · 0 comments · May be fixed by #14

Comments

@dkx-daniel
Copy link

Currently, it is not possible to communicate with web servers requesting a TLS renegotiation:

$ monsoon test --value example https://www.example.com/path/FUZZ
Target URL: https://www.example.com/path/FUZZ

 status   header     body   value    extract

    Err        0        0   example  local error: tls: no renegotiation

processed 1 HTTP requests in 0m00s
1 of 1 requests shown

To fix this, the constant RenegotiateOnceAsClient needs to be set for the TLS client configuration as suggested in this StackOverflow answer. This could be for example included in the --insecure-ciphersuites flag:

monsoon test --insecure-ciphersuites --value example https://www.example.com/path/FUZZ
Target URL: https://www.example.com/path/FUZZ

 status   header     body   value    extract

    404      228     3284   example 

processed 1 HTTP requests in 0m01s
1 of 1 requests shown
404: 1
@dkx-daniel dkx-daniel linked a pull request Aug 2, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant