search

shadowsocks / shadowsocks-go

go port of shadowsocks (Deprecated)
http://shadowsocks.github.io/shadowsocks-go
Apache License 2.0
6.61k stars 3.32k forks source link

shadowsocks-libev 3.2.1 client error #451

Closed jouyouyun closed 5 years ago

jouyouyun commented 5 years ago

My Server: shadowsocks-go 49161ddf51fc65cf557554b8909aeb82e9da5409 Client: shadowsocks-libev 3.2.1

Errors:

2018-11-13 18:15:23 INFO: initializing ciphers... aes-256-cfb
2018-11-13 18:15:23 INFO: listening at 127.0.0.1:1080
2018-11-13 18:15:41 ERROR: crypto: stream: repeat IV detected
2018-11-13 18:15:41 ERROR: invalid password or cipher
2018-11-13 18:15:42 ERROR: crypto: stream: repeat IV detected
2018-11-13 18:15:42 ERROR: invalid password or cipher
2018-11-13 18:15:48 ERROR: crypto: stream: repeat IV detected
2018-11-13 18:15:48 ERROR: invalid password or cipher
2018-11-13 18:15:48 ERROR: crypto: stream: repeat IV detected
2018-11-13 18:15:48 ERROR: invalid password or cipher
2018-11-13 18:15:48 ERROR: remote_recv_cb_recv: Connection reset by peer
2018-11-13 18:15:49 ERROR: crypto: stream: repeat IV detected
2018-11-13 18:15:49 ERROR: invalid password or cipher
2018-11-13 18:15:49 ERROR: crypto: stream: repeat IV detected
2018-11-13 18:15:49 ERROR: invalid password or cipher

But downloded shadowsocks-libev to 3.2.0, it's ok!

shadowsocks-libev issue: https://github.com/shadowsocks/shadowsocks-libev/issues/2217

arthurkiller commented 5 years ago

seems your cipher or passwd is incorrect, check your configuration

jouyouyun commented 5 years ago

No problem with cipher and passwd, it's ok on shadowsocks-libev 3.2.0 and shadowsocks-android.

arthurkiller commented 5 years ago

I have tried ss-libev and every thing goes right.

Can you put up more evidences to support your point?

arthurkiller commented 5 years ago

Or just try ss-go2

jouyouyun commented 5 years ago

Or just try ss-go2

ok

jouyouyun commented 5 years ago

It's ok after using go-shadowsocks

zachcheung commented 5 years ago

Why closed this issue? Use go-shadowsocks2 does not fix this shadowsocks-go bug, or shadowsocks-go choose not to fix it?

arthurkiller commented 5 years ago

You are free to reopen this issue or just try to fix and put up merge request.

Have an awesome day

✉️✉️✉️✉️✉️✉️✉️✉️✉️✉️✉️✉️ Arthur lee Sent from my iPhone

On Nov 29, 2018, at 3:04 PM, Zach Cheung notifications@github.com wrote:

Why closed this issue? Use go-shadowsocks2 does not fix this shadowsocks-go bug, or shadowsocks-go choose not to fix it?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

zachcheung commented 5 years ago

@arthurkiller I am not able to reopen it unless open a new duplicate issue which I don't want to. Just think this bug issue should not be closed coz still not be fixed unless won't fix.

Have a good day.