PH4NTXM

Inside PH4NTXM: #31 Firewall Supervision A firewall can be correct at boot and different five minutes later. PH4NTXM's normal-mode firewall guard polls the active ruleset every two seconds and compares its fingerprint with the expected state. Source rules are integrity-checked and syntax-checked before application, including the required NFQUEUE arrangement and disabled bypass behavior. A detected mismatch removes readiness and activates emergency Lockdown before restoration. Readiness returns after successful verification. This is ongoing, periodic supervision of the expected policy, giving Boot Pilot and Health a current protection signal instead of a one-time startup assumption. #ph4ntxm #linux #debian #os #live #privacy #security #opsec #infosec #research #tech #technology

Inside PH4NTXM: #18 Protected CPU Reporting Different system commands should not disagree about the same session. PH4NTXM builds CPU model, feature, and topology information from the generated capability profile. It installs selected read-only cpuinfo and CPU sysfs views, while protected lscpu, nproc, and free commands expose corresponding session values. Unsupported reporting options return an explicit error instead of silently promising coverage they do not provide. This gives the managed reporting paths a consistent view, with a defined boundary around the interfaces PH4NTXM actually controls. #ph4ntxm #linux #debian #os #live #privacy #security #opsec #infosec #research #tech #technology

@Viss@mastodon.social That’s huge value, saving hours of active scanning and bandwidth while delivering instant delta reports. Smart architecture, making life easier, working smarter. You got lot's of love for this one, I can definitely see the passion through the screen.

@Viss@mastodon.social Go melt some brains over there, the right hooks and some eye-catching results will definitely reach the right people, if they only could understand what they're buying they would be thankful.

Apologies for the constant rebuilds and refactoring on PH4NTXM lately. Perfectionism is a curse, and I just can't let it go. Appreciate your patience while I'm fine-tuning the beast. If you have any questions, about it feel free to ask them, I will reply and respect all of them. As well some people keep on asking me about the commit date, why it's "35 years ago". As of this one, I'll let you search the exact date of the commit, and tell me what you think it is! #ph4ntxm #linux #debian #os #live #privacy #security #opsec #infosec #research #tech #technology

@Viss@mastodon.social Man, it should try harder, zero attack pathways is too peaceful for your style!

@zleap@techhub.social Hahaha, well, I'd tell you to check at the commit exact date. If you're into Linux you will understand!

Inside PH4NTXM: #11 Authenticated DNS-over-TLS DNS deserves an explicit transport policy. In Linux and Windows modes, PH4NTXM points local resolution at Unbound and configures authenticated DNS-over-TLS forwarding. TLS authentication uses provider names and the system CA bundle, with encrypted forwarding required and no plaintext upstream fallback. The configured upstream sets follow the selected mode. Unbound also uses memory caching and conservative resolver settings, while a watchdog checks local resolution and requests a restart when the required conditions indicate a failure. Resolver availability and transport policy are both part of the design. #ph4ntxm #linux #debian #os #live #privacy #security #opsec #infosec #research #tech #technology

Update... Update! PH4NTXM includes now an overall ph4ntxm-health cli, so you can check your identity and more, including score. Almost every important spoofed value is on your screen so you can verify at any mean time that everything is safe and as expected. Thank you! #ph4ntxm #linux #debian #os #live #privacy #security #opsec #infosec #research #tech #technology

Another small improvement to PH4NTXM. The Nuke Kernel now allocates available RAM and zero-fills allocated memory before powering off. The goal has never been to add features for the sake of features. It's to make every session end as cleanly as possible while keeping the implementation simple and reliable. Small changes. Big impact. Thank you. #ph4ntxm #linux #debian #os #live #privacy #security #opsec #infosec #research #tech #technology

Inside PH4NTXM: #20 Display Persona Resolution, refresh rate, and pixel ratio form a profile together. PH4NTXM generates nominal display metadata from the selected hardware and GPU class. Laptop, desktop, gaming, and supported Apple personas receive bounded combinations, including connector identity and optional secondary-display metadata where applicable. The completed screen environment becomes input for the viewport generator and participating reporting components. Lone Wolf derives its own display state. These are managed persona values. Publishing display metadata does not physically change the monitor attached to the machine. #ph4ntxm #linux #debian #os #live #privacy #security #opsec #infosec #research #tech #technology

Inside PH4NTXM: #27 Network Drift Packet timing can change throughout a session. PH4NTXM's Network Drift uses netem to vary delay, jitter, and loss on qualifying Linux/Windows default-route interfaces. Profiles update every 20–59 seconds, with separate caps for wireless jitter and loss. Small duplication and reordering settings are also applied. Recognized tunnel, container, bridge, loopback, and ghost interfaces are skipped. This feature deliberately changes network behavior, so latency and throughput tradeoffs are real. Lonewolf does not apply this local shaping. Ιts network path follows Tor. #ph4ntxm #linux #debian #os #live #privacy #security #opsec #infosec #research #tech #technology

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

Don't bust our balls with AI guys, relax, you don't like it? Don't use it, all good. #ph4ntxm #privacy #security #opsec #infosec #research #tech #technology