ztls fallback support and renegotiation error fix #144
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.
Proposed Changes
DialTLSConfig
to add/manage client certificates . hence fallback logic is not applied at all now with fastdialer it is preserved and available by defaultrenegotiation
was not set which caused local error: tls: no renegotiation nuclei#3553 in nucleiNotes
suggesting deprecating and removing
-ztls
mode in nuclei . ZTLS currently does not support TLS1.3 as well asRenogotiation
. using fastdialer in this PR with nuclei shows using ztls mode by default causes host to skip since it does not support renogotiationSetup
checkout nuclei from projectdiscovery/nuclei#3909 which contains fastdialer from this PR
using nuclei with ztls mode
using nuclei without ztls mode (i.e implicit ztls fallback)
-ztls
flag i think we should remove it since its use cases are covered and sometimes using it causes issues