#Shadowsocks qt5 update

Time is also part of the reason why I’ve made this decision so that I can focus on coding. As for Ubuntu PPA, I don’t use Ubuntu and it makes little sense for me, a non-Ubuntu user, to maintain it since I can’t even test. I had a lot of difficulties compiling all the dependencies and linking them statically on Windows. Right, that means not even Windows binaries are provided. I will no longer maintain any binary packages except for Fedora and AppImage. Meanwhile, some of you may also notice a few changes to the project. A compiler that supports C++14 is required (e.g.Complete migration to CMake build system.Full support of Shadowsocks SIP004 URI scheme, which is widely used by other clients for QR code.Full support of Shadowsocks AEAD ciphers (requires botan >= 2.3.0).

#Shadowsocks qt5 update

A popular setup is to use shadowsocks-libev as the server, while using the Android app or shadowsocks-windows, shadowsocks-qt5 as desktop clients.īack to today’s business, after a long and painful period of refactoring and cleaning, I’m happy to announce that the new major update of Shadowsocks-Qt5 and libQtShadowsocks have finally come! The highlights are: By protocol, it means you can mix and match different implementations (or so called ports in some context) of Shadowsocks. I’ve been developing and maintaining the Qt/C++ implementation of this protocol for quite some time. Happy 2018! Shadowsocks-Qt5 3.0 and libQtShadowsocks 2.0 have now been marked as stable and released!įor people who are not familiar with Shadowsocks, it is a lightweight secure SOCKS5 proxy initially developed in China to circumvent the great firewall.