From 1cb7e2895f84d659c730efe1c0bcd18adfc39b76 Mon Sep 17 00:00:00 2001 From: Russell Ballestrini Date: Thu, 8 Jan 2026 04:52:58 -0500 Subject: [PATCH] Revert "Add egress shielding docs with redsocks + microsocks" This reverts commit eea492dd6418228454b9566e12b9584548ca6bed. --- README.md | 52 ---------------------------------------------------- 1 file changed, 52 deletions(-) diff --git a/README.md b/README.md index 6dfb073..bcfc55a 100644 --- a/README.md +++ b/README.md @@ -235,58 +235,6 @@ done This is the **inception** - each layer executes through unsandbox's remote API, so you can test any implementation using `un` (the canonical C implementation) as the runner. -## Security: Egress Shielding - -Sandbox nodes route HTTP/HTTPS through tinyproxy, but raw TCP (SSH, etc.) goes out the direct egress IP. This matters for operational security - an attacker who can trigger outbound SSH could geolocate pool nodes. - -**Solution: Transparent proxy with redsocks + microsocks.** - -``` -┌─────────────────────────────────────────────────────┐ -│ Sandbox Node │ -│ │ -│ HTTP/HTTPS ──→ tinyproxy ──────→ egress proxy IP │ -│ │ -│ SSH/raw TCP ──→ redsocks ──→ microsocks ──→ same │ -│ ↑ egress proxy IP │ -│ (iptables nat) │ -└─────────────────────────────────────────────────────┘ -``` - -redsocks intercepts ALL outbound TCP and routes through the SOCKS proxy. No per-app configuration needed. - -```bash -# Install -apt install redsocks -git clone https://github.com/rofl0r/microsocks && cd microsocks && make - -# Run microsocks (SOCKS5 proxy) -./microsocks -p 1080 - -# Configure redsocks to use it -cat > /etc/redsocks.conf <