How verity-freedom/tor-portable works
Project type and purpose
• This is an open-source, fully portable tooling bundle (“Tor Portable”) that ships a fine-tuned Tor core plus helper scripts for Windows (CMD/EXE) and Linux (SH), external integrations (IPFS/IPNS updater, Discord mods), and instructions for browser proxy extensions. Its goal is to free Tor from the browser and simplify deployment on Win7, Win8+, Linux.
File structure
• Top-level scripts (AntiTor.*, service-manager.*, updater.*, change-mode.*, conjure.sh, discord.sh, etc.) are wrappers around the Tor binary and configurations.
• No source folders—this is primarily a distribution of binaries + configuration + orchestration scripts.
• Updater scripts implement an IPNS-based update mechanism.
• Two executables (AntiTor.exe, Tor Portable core) plus many shell/CMD scripts indicate cross-platform support.
Key insights from README
• Core components: Tor Expert Bundle, custom torrc configs (default vs pro modes), Win7 patch, IPFS/IPNS updater, ZeroOmega/WebRTC Control integration, optional Psiphon.
• Workflow: user runs scripts to start Tor, enable a system service, switch modes, update, or route Discord.
• External dependencies: IPFS/IPNS pinning services, browser extensions, third-party proxy helpers.
a. Main components to represent:
• Operating System (Windows or Linux)
• Tor Core Service (Tor Expert Bundle + patched binaries)
• Configuration Manager (change-mode.sh/.cmd toggles default vs pro torrc)
• Service Manager (service-manager scripts install/uninstall Tor as a service)
• Launcher (AntiTor scripts start Tor in the foreground per session)
• Updater (updater.sh/.cmd—connects to IPNS gateway to fetch new releases)
• External Proxy Tools (Discord-*, proxifyre/tun2socks optional wrappers)
• Browser Extensions (ZeroOmega, WebRTC Control)
• External Networks: IPFS/IPNS network, Tor network, Internet
b. Relationships and interactions:
• OS invokes Launcher or Service Manager → configures and starts Tor Core
• Configuration Manager swaps torrc files before launch
• Updater contacts IPNS via pinata.cloud/ipns.ipfs.network → downloads & replaces binaries/configs
• Browser (Chrome/Firefox) talks to Tor via ZeroOmega/WebRTC Control → Tor Core → Tor network → Internet
• Optional tools (Discord mods, Psiphon) can be chained after Tor Core or used in place of Tor in browser extension settings
c. Architectural patterns/design principles:
• Modular CLI wrappers (each script has one responsibility: start, serviceize, update, patch, mode switch)
• Portable, stateless distribution: no required installation, purely file-based execution
• Layered proxy stack: application (browser/Discord) → local Tor → IPFS update layer → Tor network
d. Relevant technologies/frameworks:
• Tor Expert Bundle (tor.exe/tor binaries)
• Shell scripts (sh) and Windows batch (cmd)
• IPFS/IPNS for updates
• ZeroOmega & WebRTC Control browser extensions
• Optional third-party helpers: Psiphon, proxifyre, tun2socks