v1.8.8

Features

• ssredir - (Experimental) Transparent Proxy. Currently only supports the following platforms:
  • Linux - TCP: REDIRECT and TPROXY, UDP: TPROXY
  • FreeBSD - TCP, UDP: ipfw

BUG Fixed

• Enable TCP_NODELAY for better handshaking performance, for
  • sslocal's socks5 protocol handshaking
  • Local and Remote server shadowsocks' IV/nonce exchanging
• Ensure plugins starts before listening for sslocal
  • Eliminated those connection failures while sslocal server just started
• #191 Skip IV/nonce duplication check for plain cipher

Miscelleous

• Nightly builds on CircleCI: https://circleci.com/gh/shadowsocks/shadowsocks-rust
  • Obtain release binaries in #Artifacts, for example:
    • https://circleci.com/gh/shadowsocks/shadowsocks-rust/151#artifacts/containers/0

v1.8.7

Features

• Set RLIMIT_NOFILE on *nix systems by
  • -r, --nofile command line argument
  • nofile key in configuration file

BUG Fixed

• ssserver shouldn't use local_port in configuration to bind() before connect() or sendto()
  • Command line argument --bind-addr or -b should only accept IP or Domain

v1.8.6

Basically the same as v1.8.5, but prints the actual error while handshaking with clients. Useful if server received a repeated IV and salt (probably replay attacks).

v1.8.5

Features

• Add feature trust-dns to allow disable depending on trust-dns-resolver
  • Disabling trust-dns would significantly shrink the size of binaries
• #26 UDP servers will also bind() to local_address and local_port
• Check repeated IV / Salt for defending against replay attacks
  • Defend against replay attack

v1.8.4

Features

• ssserver supports bind before connect to remote addresses. Can be configured by
  • local_address and local_port in config.json
  • -b or --bind-address in command line parameter
    Suggestion: Port should be set to 0 otherwise you will get EADDRINUSE

Breaking Changes

• ssserver won't ignore local_address and local_port in config.json

v1.8.3

Enhancements

• Refactored PingBalancer for supporting customized Server Configuration structure

  • For Example: HTTP sslocal can stores HttpClients into the ServerScore structure instead of putting them into a HashMap.

• Removed trust-dns feature gate, set as default.

Releases

• shadowsocks-v1.8.0-stable.x86_64-unknown-linux-musl.tar.xz
  • SHA256 d4144b0c13789c8755448a6b68c8c04c46376013d340a3c8940344b1ba17bc4f
• shadowsocks-v1.8.0-stable.x86_64-pc-windows-gnu.zip
  • SHA256 f619061c143ca6c743922d0dd6daa45a6273f929b3f8c4d77b0bb42fd71b1ee4

v1.8.2

Enhancements

• Refactored PingBalancer for supporting customized Server Configuration structure

  • For Example: HTTP sslocal can stores HttpClients into the ServerScore structure instead of putting them into a HashMap.

• Removed trust-dns feature gate, set as default.

v1.8.1

BUG Fixed

• Send crypto IV (Stream Ciphers) / Nonce (AEAD Ciphers) with the first payload in one packet.
  • Reduced 1 RTT while handshaking with servers
• HTTP Proxy client Handles IPv6 URI host properly
  • RFC 2732

Releases

• shadowsocks-v1.8.0-stable.x86_64-unknown-linux-musl.tar.xz
  • SHA256 fcfbb60f0dc6ef5608ab589e3655f7979a56f0e5051b1ceac9d669da2dd53f97
• shadowsocks-v1.8.0-stable.x86_64-pc-windows-gnu.zip
  • SHA256 9d831d7d98e82d02a4eca767ba2095301656f1e1dc1a3a81c112dc26caddb2ed

v1.8.0

Features

• A new binary sstunnel. Establish TCP and UDP tunnels to remote. Discussion: #177

  # Establish an UDP tunnel to 8.8.8.8:53 (just like what ssdns did in the past)
  sstunnel -c config.json -f '8.8.8.8:53' -u
  

• Uses async/await syntax (requires rustc version >= v1.40.0)
• Dependencies
  • tokio - v0.2
  • trust-dns-resolver - v0.18
  • libsodium-sys (switched from libsodium-ffi for better build process)
• Ping balancer
  • Calculate scores not only with servers' latency, but also availablity
  • Supports UDP relay
• Retry 3 times if it connects failed to remote proxy server automatically

Bug Resolved

• Refactored UDP relay. Now it works just like NAT. Discussion: #168
• Temporary workaround for UdpSocket WSAECONNRESET. Discussion: #179
  • Ref: https://stackoverflow.com/questions/30749423/is-winsock-error-10054-wsaeconnreset-normal-with-udp-to-from-localhost

Breaking Changes

• Removed ssdns. sstunnel can fulfill its job.

Releases

• shadowsocks-v1.8.0-stable.x86_64-unknown-linux-musl.tar.xz
  • SHA256 5ec41d5a306715e455b1012de0ddaa33273970689b6df48ffbb0da5fb6083531
• shadowsocks-v1.8.0-stable.x86_64-pc-windows-gnu.zip
  • SHA256 f7e23a145ca42a0ce73349263650256c9cc3e05caf637c2396699d72801d6966

v1.8.0-alpha.4

BUG

• #179 Update UDP association expire time bi-directionally.
• #179 Temporary workaround for UdpSocket WSAECONNRESET
  • Ref: https://stackoverflow.com/questions/30749423/is-winsock-error-10054-wsaeconnreset-normal-with-udp-to-from-localhost

Features

• Migrated to libsodium-sys for more reliable build process

Releases

• shadowsocks-v1.8.0-alpha.4-stable.x86_64-pc-windows-gnu.zip SHA256: 360adf13908927e39e646af07adc30265989e4b661a1890dcfb5ee7bbaa999ee
• shadowsocks-v1.8.0-alpha.4-stable.x86_64-unknown-linux-musl.tar.xz SHA256: 5f761a54b148952897e26d969b6022393a64208d9a566e92a3fa10e014388bac