Inside PH4NTXM: #29 System Ηardening Protection services need boundaries of their own. PH4NTXM combines selected kernel restrictions with component-specific systemd controls. The native packet worker, for example, uses a restricted capability set, protected system paths, limited address families, disabled core dumps, and a watchdog. The configuration constrains what individual services can access and exposes failures through their startup or runtime checks. The live operator still has passwordless sudo, so administrative access remains a trust boundary. Hardening reduces available interfaces within that model. Ιt does not survive a fully compromised kernel by assumption. #ph4ntxm #linux #debian #os #live #privacy #security #opsec #infosec #research #tech #technology