Apranik

Guides ​

Task-based walkthroughs with complete config files. Each pair is a server, run on a machine outside the censored network, and a client, run on the user's device, which exposes a local SOCKS5 or mixed port for apps.

A client and a server: an app on the user's device talks SOCKS5 or HTTP to the local apranik client, whose outbound is a Trojan proxy over TLS. Across the censored network a DPI box sees only a TLS connection to the server's name. On the server, an apranik inbound with the Trojan protocol over TLS passes the request to freedom, which connects to the real destination.

What these guides assume ​

Replace proxy.example.com, the passwords and the certificate paths with your own. Check a file before running it:

sh
apranik check -config server.json
apranik run -config server.json

A client's local port with no users is open to every app on the machine.

The protocol and transport pages describe every setting: trojan, tls, ws, httpupgrade.

The guides ​