TTP v0.3.0: Amnesia Core

The transition to version 0.3.0 introduces a major architectural shift focused on process isolation and forensic invisibility. The application core has been redesigned to operate almost entirely in volatile memory, trying to minimize physical traces on the disk following a reboot.

Disclaimer: This is not forensically reliable because the Linux distro beneath it (let it be Arch, RHEL, etc.) are NOT designed for such purpose. So, traces on the OS/Kernel level are present. If you are looking reliable tools, please, use TailsOS, the TOR Browser, etc.

Core Changes

• Amnesia Architecture: All runtime state, lock files, and system logs now reside strictly in /run/ttp (tmpfs). Data evaporates physically when the system is powered off or rebooted.
• Service Isolation: A dedicated, volatile systemd unit named ttp-tor.service is now generated dynamically at runtime. This service operates independently, avoiding permission conflicts with the default system Tor sandbox.
• Port Shifting: To allow seamless coexistence with pre-existing Tor instances, traffic routing is now shifted to custom ports 9041 (TransPort) and 9054 (DNSPort). Background Tor relays or onion services can operate simultaneously without encountering port conflicts.
• Stateless DNS Overlay: Destructive editing of /etc/resolv.conf has been replaced by a kernel-level mount --bind overlay. The original system DNS configuration remains completely untouched on the physical disk.
• Unix Control Sockets: Daemon management is now handled natively via private Unix sockets mapped in RAM, eliminating the exposure of local TCP control ports.

Improvements

• Fast Bootstrap: Entry Guards are preserved within a dedicated persistent cache, reducing circuit initialization time to approximately 3 seconds.
• Safe Teardown: A cryptographic circuit shutdown is executed prior to releasing firewall rules to prevent cleartext packet leaks on the physical interface.
• Pre-flight Checks: Mandatory system state verification and RAM availability checks are performed prior to startup to prevent mid-execution failures.

The update can be applied by re-running the global installation script or deploying the latest pre-compiled package artifacts.