Support basic socks5 authentication
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
This is for security reason. Socks5 supports username/password based authentication (https://tools.ietf.org/html/rfc1929).
In certain environment, we want to make sure only authenticated user can access the socks5 proxy (our case is in the reverse tunnel case, where the socks5 proxy server is running at the server side).
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 by reading RFC1929 and tracing chisel's SOCKS5 proxy and reverse-tunnel entry points to identify where authentication is negotiated. Define the supported username/password behavior for the server-side SOCKS5 proxy and add tests covering accepted and rejected credentials; done means unauthenticated access is blocked when authentication is enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100