Kebin Liu 719203afc6 Merge pull request #1501 from hiddenSharp429/develop | il y a 1 mois | |
---|---|---|
.github | il y a 1 mois | |
LaunchHelper | il y a 1 an | |
Pods | il y a 3 ans | |
ShadowsocksX-NG | il y a 1 mois | |
ShadowsocksX-NG.xcodeproj | il y a 1 an | |
ShadowsocksX-NG.xcworkspace | il y a 7 ans | |
ShadowsocksX-NGTests | il y a 3 ans | |
deps | il y a 1 an | |
proxy_conf_helper | il y a 5 ans | |
.gitignore | il y a 1 an | |
.gitmodules | il y a 1 an | |
LICENSE | il y a 8 ans | |
Makefile | il y a 1 an | |
Podfile | il y a 3 ans | |
Podfile.lock | il y a 3 ans | |
README.md | il y a 3 ans | |
_config.yml | il y a 8 ans | |
genstrings.py | il y a 8 ans |
Next Generation of ShadowsocksX
It's hard to maintain the original implementation as there is too much unused code in it.
It also embeds the ss-local
source code. It's crazy to maintain dependencies of ss-local
.
So it's hard to update the ss-local
version.
Now I just copied the ss-local
from Homebrew. Run ss-local
executable as a Launch Agent in the background.
So there is only some source code related to GUI left.
Then I have rewrited the GUI code in Swift.
macOS 10.12+
From here
ss-local
from shadowsocks-libev 3.2.5.kcptun
, simple-obfs
and v2ray-plugin
.ss-local
is run as a background service through launchd, not as an in-app process.
So after you quit the app, the ss-local
might be still running.
Added a manual mode which won't configure the system proxy settings, so that you could configure your apps to use the SOCKS5 proxy manually.
Contributions must be available on a separately named branch based on the latest version of the main branch develop
.
ref: GitFlow
The project is released under the terms of the GPLv3.