shadowsocks-android icon indicating copy to clipboard operation
shadowsocks-android copied to clipboard

libsslocal exits too fast (exit code: 134) after set any 2022-* cipher

Open sem-hub opened this issue 1 year ago • 0 comments

Please read contributing guidelines. Thanks.

Describe the bug I used chacha20-ietf-poly1305 and it worked well. After I set any 2022-* ciphers (for both client and server) I have got libsslocal exits too fast (exit code: 134) message on connect (even without any connection try). I've tested 2022-blake3-chacha20-poly1305 cipher with a desktop client and it worked well but not with android client.

To Reproduce Steps to reproduce the behavior: Set any 2022-* cipher.

Expected behavior Connect to server.

Screenshots libsslocal exits too fast (exit code: 134) message in android client.

Smartphone (please complete the following information):

  • Android/Chrome OS version:12 (security patch from 12/05/22)
  • Device: OnePlus 7T
  • Version: 5.3.3
  • Last version that did not exhibit the issue: [not applicable]

Configuration Put an x inside the [ ] that applies.

  • [X] IPv4 server address
  • [ ] IPv6 server address
  • [X] Client IPv4 availability
  • [ ] Client IPv6 availability
  • Encrypt method: 2022-blake3-chacha20-poly1305 (really any 2022-*)
  • Route
    • [X] All
    • [ ] Bypass LAN
    • [ ] Bypass China
    • [ ] Bypass LAN & China
    • [ ] GFW List
    • [ ] China List
    • [ ] Custom rules
  • [ ] IPv6 route
  • [ ] Apps VPN mode
    • [ ] Bypass mode
  • Remote DNS: 8.8.8.8
  • [ ] DNS over UDP
  • Plugin configuration (if applicable):
  • [ ] Auto Connect
  • [ ] TCP Fast Open
  • If you're not using VPN mode, please supply more details here:

Additional context I increased my password from 20 to 32 symbols as server asked. But after I back to chacha20-ietf-poly1305 it works with 32 symbols password too. I watched traffic on my server and see no connection tries from android client when error showed.

sem-hub avatar Feb 16 '24 00:02 sem-hub