shadowsocks / shadowsocks/shadowsocks-org
Recent White List issues
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1k
- Forks
- 694
- PR merge metrics
- No merged PRs in 30d
Description
As we know, some ISP use white list (port and more?) recently, and the logic is:
TCP handshake --> pass
Server First Return packet --> pass
Client first packet --> filtered
As they need to white-list some site, so if the Server First Return packet match pattern and port of white-list site, maybe they'll let client first packet pass.
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 TCP handshake sequence described in the issue: the server-first return packet and the client-first packet. Determine whether the proposed whitelist behavior is an accepted project requirement; done would require a decided scope and an identified implementation location, neither of which the issue currently provides.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100