shadowsocks / shadowsocks/shadowsocks-rust
shadowsocks crate issues
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.9k
- Forks
- 1.5k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 5
Description
After using the shadowsocks crate, the port was easily detected. I used go-shadowsocks2 for two years without such issues. Now, after switching back to go-shadowsocks2 (with a different port) for a month, everything seems normal so far.
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 comparing the shadowsocks crate with go-shadowsocks2, focusing on the reported port-detection behavior. The issue names no files, tests, versions, configuration, or reproducible steps, so first collect those details and establish a reliable reproduction. Done should mean the behavior is reproduced, its cause is identified, and a verified mitigation or fix is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100