database64128
database64128
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I'm a maintainer on https://github.com/shadowsocks/shadowsocks-windows. I approve this message. -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQRNztFeNG4pI7kx1vcconVGvtuLAQUCYCJBmwAKCRAconVGvtuL AdrQAQC7dJA3qiRtM3abzZWHFlNhAYi56NWe+T1DVcUmI9ndkQD8DuBveRJ7LeRS /hIImh8cuZF8Zt/tv8WWaXjxQdIKqAY= =RclQ -----END PGP SIGNATURE-----
Why do you need AppImage?
In https://github.com/RustCrypto/AEADs/issues/243#issuecomment-748914592, 16B data is used for AES-GCM tests. I bumped the data size to 8 KiB, updated all crates to the latest version, and reran some of the tests....
Your key length is not 32 bytes.
> len(12345678901234567890123456789012) = 32 This is not a key. The key should be a slice of 32 bytes, not a string of 32 characters.
> start a lot of port listeners I don't think starting thousands of listeners is how you are supposed to use the server. You might want to use Shadowsocks 2022's...
Instead of trying to fix this mess, maybe consider switching to a modern alternative instead: - https://github.com/database64128/shadowsocks-go - https://github.com/SagerNet/sing-box Both of these use my https://github.com/database64128/tfo-go for TFO support on Linux,...
@hdid UoT is not part of the Shadowsocks 2022 protocol. Related discussions: shadowsocks/shadowsocks-rust#834
@hdid https://github.com/shadowsocks/shadowsocks-rust/issues/834#issuecomment-1121254412
> @database64128 also implemented another way to bypass the censorship. Because the protocol is changed, it requires updating both client and server to use it. I wouldn't call it a...