What the PH4NTXM developer told us

This morning we published a remarkable effort by a Greek programmer, who envisioned and created PH4NTXM, the first Linux OS by a Greek developer that aims for security and privacy. His name is Geo Bountalakis and you can find him on Mastodon: @geobountalakis@defcon.social

The official project handle: https://defcon.social/@PH4NTXMOFFICIAL

See more articles from iGuRu.gr when you search for news on Google.

iGuRu.gr preferred source

Let's see what he told us.

PH4NTXM started as a personal project by a single developer and was born from a very simple need, I was just looking for something that I couldn't find in existing security distributions.

I wanted a system that I truly knew from start to finish. To know how it was set up from scratch, what it included, and perhaps more importantly, what it didn't. From the first package to the last, I wanted every option to be there for a reason and to be there because I chose it, not because it was inherited from some pre-made environment or because "that's how it's usually done."

PH4NTXM is a live operating system built around cybersecurity and privacy. It was not designed to be installed and leave behind a permanent state on the machine. It runs exclusively in RAM, so each boot is a new session and, when it is completed, the state created within the operating system itself is lost with it.

This to me is not just a technical feature. It is a fundamental part of the PH4NTXM philosophy. Being live, RAM-only, and stateless is what gives us the foundation on which we can build the idea of ​​disposable identity and session decoupling.

At the same time, it provides a ready-made environment with privacy and security protection mechanisms, along with the tools one needs for pentesting and cybersecurity work in general . It also includes mechanisms that I thought of and added as a paranoid user would think, to put it simply.

But what I want to differentiate it from is not just its collection of tools. One of the main problems it tries to address is correlation, that is, the association of different sessions or the activity of an operator.

To me, correlation means the ability of a third party to link two different sessions together and conclude that the same identity or system is behind them, even when these sessions originate from the same USB.

And that's where the RAM-only model comes in. I don't just want to delete some files at the end. I want the system architecture itself to start from the assumption that the session is temporary and that there's no reason to carry permanent state with it on the next boot.

To me, disposable identity means something that is truly temporary. An identity that is created for a specific session, used, and then ceases to exist, without the operating system itself maintaining any permanent state that could later be used to connect one use to the next.

The logic of PH4NTXM is to make the most of this stateless model and give the user control over how they move within it. We don't want the operating system to decide for them. We want to give them the mechanisms to choose how isolated, temporary, and difficult to relate to each session.

And here I think it's important to be honest. Operational security is us, not the tools. PH4NTXM may be live, RAM-only, and try to limit what the operating system itself leaves behind, but it can't control what a remote server logs or correct a bad choice by the operator. The human remains the last link in the chain.

PH4NTXM has advanced mechanisms designed to assist the user in critical potential scenarios. However, no mechanism can replace the knowledge and judgment of the operator himself. Reading the documentation and understanding how the system works remains essential so that the user can properly utilize its capabilities, but also be aware of their limitations.

Through mechanisms like the OPSEC Suite we also try to give the user live diagnostics and the clearest possible picture of what is happening in their system at any given moment. The goal is not to create a false sense of security, but to give the operator the information and tools he needs to make informed decisions.

The difficulties in its development were many. One of the biggest was to turn these ideas into real implementations and not just promises. At the same time, the system had to be able to run on different hardware, remain as light as possible in requirements, and at the same time reliably execute the mechanisms that we consider essential for the project, such as nuke termination and other security functions.

There were periods of intense burnout. But there was never a moment when I really thought about leaving PH4NTXM for good. Maybe because the same reason it was started is still there. It is a system that I wanted to exist for myself first and foremost.

PH4NTXM started with one person, but I don't want it to end there. As the project opens up to the community, the "I" gradually becomes "we".

The vision for PH4NTXM is not to become an operating system that people will trust because we tell them to trust it.

It's exactly the opposite.

Trust after verification.

We want the user to be able to see, check, try and only then decide if PH4NTXM is worth their trust. In security, after all, trust without verification should not be considered enough.

And to anyone meeting PH4NTXM for the first time today, the message is simple:

Download it, run it, try it, search it, that's the policy for protection, knowing what you're dealing with.

And if you find something wrong, something that could be done better, or something that isn't working as it should, come and let's fix it.

Because PH4NTXM may have been started by one person, but the purpose is not to remain the property of one person.

PH4NTXM belongs to the community. To all those who believe that privacy is not a luxury and that security should be verifiable. We all strive for the best and that is why we are open to any new idea that is consistent with the architecture and philosophy of the project. As long as it really offers something to the user. Not something that exists just for show, but something that essentially gives new possibilities, new options and different ways to approach what we have taken for granted until now.

newsbot

Although the press releases will range from very select to rare, I said I'd pass...because sometimes the editors hide.