Closed aquaman1984 closed 1 year ago
设备 pixel 5 系统Android 13 TQ1A.230205.002 全部配置文件都是ss2022的,有ipv4,ipv6,全局,开启绕行,开代理ipv6。 5.32没事,升到5.3.3是时候发生了这个,7个本地配置文件有3个都出问题,新建一个一模一样的配置文件却可以运行,把有问题配置文件的加密方式改成流加密也可以运行。
Is there any known issue of aead-2022-cipher feature on ARM? @zonyitoo
Nope. I run it everyday on my ARM router (aarch64) with various encryption methods, including aead, aead-2022, and didn't see any problems like this.
Consider rebuilt with the latest library code and see if the problem fixed. :)
02-15 21:20:03.495 15385 15385 F DEBUG : Abort message: '2022-blake3-chacha20-poly1305 password example is not base64 encoded, error: Encoded text cannot have a 6-bit remainder.
@Mygod it looks we need to output the error message in a better way. Or we can check if the key is base64 encoded for aead-2022-cipher first.
@iamsad3508 Make sure you provide a valid base64 encoded shared key for aead-2022-cipher
@madeye 为什么会缺了两个 ”==“ ? 补回去就好了,我不太确定之前5.3.2的时候等号是否在,反正之前一直正常在用
v5.3.2没有“==”也可以正常使用,应该是升到5.3.3就不可以了
Maybe you have built with the latest master branch? The latest base64
crate will validate the string and report error if it is not a valid standard base64 string.
Or we can check if the key is base64 encoded for aead-2022-cipher first.
That would be better.
Well yes, it is a new "feature" from base64
. :P
I am using version 5.3.2 and when I connect to shadowsocks 2022 I get the error I posted in the title.