❓ Limit to specific ports (question regarding --auth and --authfile)
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Thank you for this great project, and sorry to bother you!
Can you please provide some examples to limit Chisel server to only allow connection to certain ports (e.g. 8080) from the client side, without using a username/password?
Something like this:
--auth *:8080
Should I use a regex pattern like this? ^(localhost|127\.0\.0\.\d+:|\[::1\]):8080$
I currently run chisel on the server like this:
./chisel --port 80
Any help would be appreciated!
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 with the Chisel CLI entry point and inspect the documented behavior of --auth and --authfile alongside the example command ./chisel --port 80. Confirm whether unauthenticated, port-specific client restrictions are supported, then document a working example or clarify the limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, networking
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100