2017-07-22 Update: See my post to find out how to upgrade to 3.0.x.

今天把Shadowsocks-libev升级到了3.0.1,无法正常使用。折腾了一下,没有修好,想到会不会是Arch的激进更新导致的,就把它后退到2.x系列了,马上就好了。

去看了一下更新日志,有这样的字眼:

shadowsocks-libev (3.0.1-1) unstable; urgency=medium

  • Fix a crashe when using stream ciphers.
  • Fix a protocol bug in AEAD ciphers. (SIP004)
  • Allow setting keys directly. (SIP006)

– Max Lv [email protected] Tue, 07 Feb 2017 13:18:02 +0800

shadowsocks-libev (3.0.0-1) unstable; urgency=medium

  • Drop dependencies of OpenSSL and PolarSSL.
  • Deprecate OTA (One-Time-Auth).
  • Add new ciphers for SIP004: aes-128-gcm, aes-192-gcm, aes-256-gcm,
    chacha20-poly1305 and chacha20-ietf-poly1305.
  • Refine SIP003 to support standalone mode of obfsproxy.

– Max Lv [email protected] Wed, 01 Feb 2017 19:10:14 +0800

3.0.0丢弃了One-Time-Auth和OpenSSL,和之前的版本不大一样了,而且,看说明文档,没有提Windows版本的编译,搞不好也丢弃了Windows平台。既然有严重的兼容性问题,为何要升级呢?

2017-03-07 Update: 丢弃OTA支持似乎和安全有关,网上有相关讨论,想看自己搜索罢,我没看懂。Windows的话可以用这个

https://github.com/Windendless/shadowsocks-libev

但我的服务端还没升级3.0.x,所以我选择先不升级。