ee039ca596
* Fix isOverDataLimit logic to stop allowing 0 traffic byte issue #1515 This if statement is just wrong and doesn't block access when traffic limit is set to 0 byte. This one character fixes it. Now if we create a new access key, set the limit to 0 before first usage, the client no longer will be able to connect. * Rename `isOverDataLimit` to `reachedDataLimit`. * Add a test case to prevent regression. * Rename old variable. * Update comment now that variable has changed meaning slightly. Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com> --------- Co-authored-by: sbruens <sbruens@users.noreply.github.com> Co-authored-by: Vinicius Fortuna <fortuna@users.noreply.github.com> |
||
|---|---|---|
| .github | ||
| docs | ||
| scripts | ||
| src | ||
| third_party | ||
| .browserslistrc | ||
| .clang-format | ||
| .dockerignore | ||
| .editorconfig | ||
| .eslintignore | ||
| .eslintrc.json | ||
| .gitallowed | ||
| .gitignore | ||
| .npmrc | ||
| .nvmrc | ||
| .prettierignore | ||
| .prettierrc.json | ||
| .shellcheckrc | ||
| commitlint.config.js | ||
| CONTRIBUTING.md | ||
| go.mod | ||
| go.sum | ||
| jasmine.json | ||
| LICENSE | ||
| package-lock.json | ||
| package.json | ||
| README.md | ||
| Taskfile.yml | ||
| tools.go | ||
| tsconfig.json | ||
Outline Server
Outline Server is the component that provides the Shadowsocks service (via outline-ss-server) and a service management API. You can deploy this server directly following simple instructions in this repository, or if you prefer a ready-to-use graphical interface you can use the Outline Manager.
Components:
-
Outline Server (
src/shadowbox): The core proxy server that runs and manages outline-ss-server, a Shadowsocks backend. It provides a REST API for access key management. -
Metrics Server (
src/metrics_server): A REST service for optional, anonymous metrics sharing.
Join the Outline Community by signing up for the IFF Mattermost!
Shadowsocks and Anti-Censorship
Outline's use of Shadowsocks means it benefits from ongoing improvements that strengthen its resistance against detection and blocking.
Key Protections:
- AEAD ciphers are mandatory.
- Probing resistance mitigates detection techniques.
- Protection against replayed data.
- Variable packet sizes to hinder identification.
See Shadowsocks resistance against detection and blocking.
Installation
Prerequisites
-
Install dependencies
npm install -
Start the server
./task shadowbox:startExploring further options:
- Refer to the README: Find additional configuration and usage options in the core server's
README. - Learn about the build system: For in-depth build system information, consult the contributing guide.
- Refer to the README: Find additional configuration and usage options in the core server's
-
To clean up
./task clean