This commit changes the "method" parameter in the debian/config.json
from "rc4-md5" to "chacha20-ietf-poly1305". rc4-md5 is unsafe and
there is support for a better AEAD ciphersuite.
Commit f32ac38c2f
allows to use pwgen to generate the initial password at the first
installation. However it won't work when apg isn't installed because:
* the postinst script has errexit option set ("set -e")
* at the first installation of ss-libev, apg or pwgen will be called to
generate the initial password in config.json
* when apg isn't installed, "pathfind apg" would return 1
* and the postinst script will immediately exit due to "set -e"
This commit temporarily turn off the errexit option for pathfind()
Commit f32ac38c2f
allows to use pwgen to generate the initial password at the first
installation. However it won't work when apg isn't installed because:
* the postinst script has errexit option set ("set -e")
* at the first installation of ss-libev, apg or pwgen will be called to
generate the initial password in config.json
* when apg isn't installed, "pathfind apg" would return 1
* and the postinst script will immediately exit due to "set -e"
This commit temporarily turn off the errexit option for pathfind()
debhelper 10 is available in the following Debian/Ubuntu releases:
- Debian 8.x Jessie (jessie-backports)
- Debian 9.x Stretch / unstable
- Ubuntu 16.04 Xenial (xenial-backports)
- Ubuntu 16.10 Yakkety
debhelper supports dh-autoreconf and dh-systemd by default, so we can
safely remove a few Build-Depends and dh params.
We also sync a few other files under debian/ folder with Debian release
3.0.2+ds-1~exp1.
This commit will fix .deb packaging instructions for Ubuntu 16.04.
Meanwhile, .deb packaging for Debian/Ubuntu is now only suitable
for Ubuntu 16.04 LTS or higher, Debian 9 or higher.
Debian 8 users won't be able to build from source too because this
project now requires libsodium >= 1.0.8. Jessie-packports is needed
to build on Debian 8.
Add experimental HTTP/TLS obfuscating as an **optional extension** of shadowsocks protocol.
More discussions can be found here: https://github.com/shadowsocks/shadowsocks-org/issues/26
As this feature is still a SIP (Shadowsocks Improvement Proposal), it's very unstable and experimental. So,
1. Don't enable it unless you know what it is.
2. Be very careful when using it in production environment.
Max Lv
Daniel
Rick Lei
Patrick Li
Roger Shimizu
Boyuan Yang
Zhengjun Zhang
Rayson zhu