shadowsocks / shadowsocks/shadowsocks-org
SIP024: Add 0/1 adjust for Shadowsocks
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1k
- Forks
- 694
- PR merge metrics
- No merged PRs in 30d
Description
SIP024: Add 0/1 adjust for Shadowsocks
Background
I am writing regarding the protocol enhancement discussion initially presented in this GitHub issue.
Context
Since 2021, the effectiveness of fully encrypted traffic protocols, including Shadowsocks and Vmess, has been significantly impacted by advanced filtering mechanisms. This situation necessitates the implementation of innovative solutions to maintain protocol functionality.
Recent Developments
A comprehensive research paper published in 2023 (USENIX Security '23) has presented a promising solution involving the implementation of 0/1 adjustments for the Shadowsocks protocol. While @gfw-report has successfully developed a proof-of-concept implementation, there remains a notable limitation regarding Shadowsocks2022 compatibility.
Proposed Solutions
Primary Proposal
I would like to respectfully request consideration for implementing 0/1 adjustment support for Shadowsocks2022. This enhancement would significantly improve the protocol's resilience while maintaining its core functionality.
Alternative Approach
As an alternative solution, the development of an obfuscation plugin for ShadowsocksR could be considered. This approach offers several advantages:
- Maintains the integrity of the base ShadowsocksR implementation
- Provides a modular solution that can be easily implemented
- Offers flexibility in deployment and maintenance
Request
I would greatly appreciate your consideration of these proposals, particularly the implementation of 0/1 adjustment support for Shadowsocks2022. Your expertise and contribution to this matter would be invaluable for the continued development and improvement of these essential protocols.
Thank you for your time and consideration.
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 implementation files, tests, or entry points are named in the issue. Start by reviewing the linked research paper, the referenced proof-of-concept, and existing Shadowsocks2022 compatibility constraints; done would require a decided approach and an implemented, compatible 0/1 adjustment or obfuscation solution.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100