Support socks5:// protocol as client proxy protocol
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
The current version of chisel only allows the client to use socks:// or socks5h:// as proxy protocol:
However, Golang only supports the socks5:// proxy protocol for its HTTP client:
This leads to a conflicting situation when using a Go program that uses both the standard HTTP client and the chisel client and needs to go through a SOCKS proxy (such as the portainer agent).
Was there any reason to only allow for the socks:// instead of socks5:// in the chisel client?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in client/client.go at lines 273-279, then compare the accepted proxy schemes with Go's net/http transport behavior linked in the issue. Done means the chisel client accepts socks5:// alongside the existing supported schemes and remains compatible with SOCKS proxy usage in Go programs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100