Authenticated policy boundary
Basic or token authentication, user policy, request controls, and bounded rate handling precede forwarding.
Pinned project · Privacy infrastructure
Main CI + security scans green · operator-managedAuthenticated Privacy Proxy
A containerized Mitmproxy–Privoxy–Tor chain that makes ingress authentication, request policy, DNS behavior, egress routing, and host automation explicit and inspectable.
Engineering thesis
Privacy is a routed system, not a product label.
The stack separates authenticated ingress, policy enforcement, HTTP forwarding, Tor egress, and DNS resolution into inspectable service boundaries. Runtime configuration and operator controls determine the effective outcome.
Docker Compose, Make targets, and Debian host automation provide reproducible setup and verification paths without claiming that infrastructure automation proves a hardened deployment.
Implemented controls
What the repository demonstrates
Layered egress path
Mitmproxy, Privoxy, and Tor own distinct responsibilities with stream-isolation and node-policy controls.
Local resolver contract
Unbound provides local resolution, DNSSEC configuration, optional DNS-over-TLS, and blocklist input.
Automated, reviewable setup
Container builds, smoke checks, TLS modes, firewall guidance, service setup, and update tasks are explicit.
Operational boundary
The stack does not guarantee anonymity.
- Operators remain responsible for ingress exposure, firewall policy, credentials, certificates, logging, patching, and jurisdiction-specific TLS interception requirements.
- Tor routing and geographic node policy change traffic paths; they do not prove anonymity, unlinkability, availability, or endpoint safety.
- Repository CI validates source and configuration paths, not the security posture of an arbitrary deployed host.