shadowsocks / shadowsocks/shadowsocks-org
Defend against replay attack
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1k
- Forks
- 695
- PR merge metrics
- No merged PRs in 30d
Description
https://en.wikipedia.org/wiki/Replay_attack
A replay attack (also known as playback attack) is a form of network attack in which a valid data transmission is maliciously or fraudulently repeated or delayed. This is carried out either by the originator or by an adversary who intercepts the data and re-transmits it, possibly as part of a masquerade attack by IP packet substitution.
Replay Attack potentially allows adversaries to identify a Shadowsocks server by observing and replaying the data streams between a valid client and the server. Ideally we want to recognize that a data stream is replayed, and react accordingly.
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 issue description and its linked Wikipedia article to understand the replay-attack threat against Shadowsocks data streams. No implementation files, entry points, or tests are identified in the issue; done would require an agreed way to recognize replayed streams and a defined response, followed by corresponding implementation and validation.
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