[Feature Request] client --socks5 & R:1080:socks
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
currently we need to run external socks server for this to work:
user --> chisel server --reverse <----> chisel client server 1080:somesocks:1080 ---> somesocks -->
having socks server in the client would remove that requirement:
user --> chisel server --reverse <----> chisel client server --socks5 R:1080:socks --->
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 at the chisel client command and its flag handling, then trace how reverse tunnel endpoints are created. Review the existing client forwarding path and the SOCKS5 request flow described in the issue. Done means the client accepts --socks5 R:1080:socks and provides the requested SOCKS5 forwarding without an external SOCKS server.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100