How could configure authfile when using remote socks
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
HI,
chisel version: chisel_1.7.7_linux_amd64
server runs:
chisel-server server --reverse --socks5 -p 28080 --authfile users.json2
users.json2:
{
"root:toor": [
""
],
"foo:bar": [
"^0.0.0.0:3000$"
],
"foo:bar2": [
"^0.0.0.0:3000$",
"^socks$"
],
"ping:pong": [
"^0.0.0.0:[45]000$",
"^example.com:80$",
"^R:0.0.0.0:7000$"
]
}
client runs:
chisel-client client --auth foo:bar2 127.0.0.1:28080 socks
failed error logs:
> 2024/06/05 15:11:26 client: Connecting to ws://127.0.0.1:28080
> 2024/06/05 15:11:26 client: tun: proxy#127.0.0.1:1080=>socks: Listening
> 2024/06/05 15:11:26 client: Connection error: server: access to ':' denied
> 2024/06/05 15:11:26 client: Give up
so how could I configure the authfile correctly when use socks proxy?
thx
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
No source file or test is named in the report. Reproduce the server and client commands with the supplied users.json2 entries, then trace how --authfile permissions are checked for the socks connection. Done means identifying the valid configuration or confirming a reproducible authentication failure and documenting the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- authentication, cli, networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100