-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chacha20 一直在客户端报错 #61
Comments
|
@zonyitoo 对,只换了加密方式。 |
是指连接的shadowsocks server使用的实现 |
server/client 都是这个项目编译出来的 |
cc @quininer Please check this issue about |
那至少这个项目里的sslocal和ssserver的包是可以互相解密的吧 |
|
按 @sbwtw 的描述,是同一个 |
server 的日志:
client 的日志:
chrome 的报错信息:
同样的配置仅仅改了加密方式到 aes-256-cfb 之后是正常的,所以不是密码错误的问题 |
確實是 ic 的原因導致的。現在的 StreamCipher 並不是真的 Stream ,不滿足 在本地會因爲 IO 太快測試不出來… |
这个你可以切换成你自己写的sodium binding啊,在 https://download.libsodium.org/doc/bindings_for_other_languages/ 都被官方认可了。这样就不用纠结另外一个库什么时候添加 *_xor_ic 了 |
名字在crates.io上被人占了 :( |
我建議刪除其他 cipher,只支持 ring 的 aead。 |
只为了backward compatibility. |
@sbwtw 可以试一下最新的commit,试一下看看chacha20能不能用? |
@zonyitoo |
shadowsocks-latest-release.x86_64-unknown-linux-musl.tar.gz |
Removed sodiumoxide, use self contained libsodium-ffi
Removed sodiumoxide, use self contained libsodium-ffi
Removed sodiumoxide, use self contained libsodium-ffi
很奇怪,server 和 client 都没有报错,访问的地址也是正常的,就是浏览器这边一直连接失败。 |
Removed sodiumoxide, use self contained libsodium-ffi
Removed sodiumoxide, use self contained libsodium-ffi
Removed sodiumoxide, use self contained libsodium-ffi
Fixed bug, wrong |
Removed sodiumoxide, use self contained libsodium-ffi
Removed sodiumoxide, use self contained libsodium-ffi
测试了最新提交,android shadowsocks 客户端和 shadowsocks-rust 的客户端都没有问题了 |
Fixed. Will be released with v1.6.2. |
换 aes-256-cfb 则没有任何问题
The text was updated successfully, but these errors were encountered: