Add support for socks5 #471
Open
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
|
Running I'm getting an error on this: Doing schema validation...
Validating zgrab-output/socks5/socks5.json [{(
{"domain":"target","data":{"socks5":{"status":"unknown-error","protocol":"socks5","result":{"version":"0x05","method_selection":"0500","connection_response":"05050001ac110002bab7","connection_response_explanation":{"Address Type":"0x01 (IPv4 address)","Bound Address":"172.17.0.2","Bound Port":"47799","Reply":"0x05 (connection refused)","Reserved":"0x00","Version":"0x05 (SOCKS Version 5)"}},"timestamp":"2025-01-25T18:30:15Z","error":"error during connection request: connection request failed with response: 05050001ac110002bab7"}}}I'll circle back to fixing this later, if anyone wants to take a stab at fixing it in the meantime feel free. |
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.
Add support for socks5.
Scanning on port 1080 by default.
Tested the protocol locally with 3proxy server.