clients are not disconnected when auth file is replaced
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 16.6k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
- allow some clients in auth file
- run chisel server with that auth file
- clients connect, OK
- delete clients from the auth file
- clients still use their old established connections - BAD
- new connections from the same clients rejected - GOOD
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 reproducing the six-step scenario against a chisel server using an auth file. Trace how auth-file replacement is handled and how established client connections are tracked; done means removed clients are disconnected while new connections from them remain rejected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100