shadowsocks / shadowsocks/shadowsocks-rust
Decryption failure error occurred when sending data: shadowsocks::relay::tcprelay::utils: copy bidirection ends with error: decrypt data failed
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 10.9k
- Forks
- 1.5k
- Avg merge
- 4d 15h
- Merged PRs (30d)
- 5
Description
Linux server, Linux client (Windows client has no problem sending small amount of data, but this error will still appear when uploading more data)
The outbound data flow is purely problematic. I have been looking for the problem for a long time. Today, I opened the debug log and checked in verbose mode: tokio-runtime-worker ThreadId(02) shadowsocks::relay::tcprelay::utils: copy bidirection ends with error: decrypt data failed, a_to_b: Running(CopyBuffer { read_done: false, pos: 0, cap: 0, amt: 0, .. }), b_to_a: Running(CopyBuffer { read_done: false, pos: 173, cap: 173, amt: 173, .. })
It can receive data normally, but it only appears when sending data. I am not sure if it is a problem with my client operating system or some other reason.
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 Linux client-to-server upload with verbose logging and tracing the bidirectional copy error in shadowsocks::relay::tcprelay::utils. Compare the outbound decryption path with the working receive path; done means identifying the cause and verifying that larger uploads no longer produce "decrypt data failed".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100