Using auth.json file with target verification
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Hi
I'm using a reversed chisel server with an auth.json file, for example:
{
"user1:123": ["R:0.0.0.0:5555"]
}
On some remote machine I'm running chisel client with the following command:
.\chisel client --auth "user1:123" <my-server-ip> R:0.0.0.0:5555:<remote-server-ip>
Everything works fine with this setup and the chisel client is authenticated and is limited to 0.0.0.0:5555 only, however I would also like to limit the remote server (<remote-server-ip>) so that the chisel server will only allow port forwarding to closed set of remotes per user, is there a way to do it as well?
Thanks
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 tracing how the server reads auth.json and how the client command's remote-server-ip target is validated. Determine whether per-user restrictions can cover both the forwarded local port and remote destination, then document the expected configuration and verification behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authorization, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100