Computers, linux, servers, parkour, bike and chess, in that order.
- Security research on rust software already deployed in production, often rust rewrites like the git rust rewrite or the coreutils rewrite (uutils).
- Contributing to linux distributions like Openmandriva where I'm one of the 60 core team members.
- Making fast software in C, secure software in rust or rapid prototypes in python
- Creating my own future-proof linux distribution with near-native support for windows apps executing from the file manager as a PoC.
Examples of my best work include:
- finding CVE-2025-64517 in sudo-rs that allowed full root privilege escalation alongside a lot of other interesting mild issues. Here's the github security advisory, the debian security advisory. This vulnerability also got covered in a dedicated video by one of the most prominent linux journals, the lunduke journal, wow!
- and various other fun stuff along the way (peek at my PR/commit history and you'll probably see something fun!)
| TempleOS | Gentoo | Arch Linux | OpenMandriva |
|---|---|---|---|
![]() |
| Linux from Scratch | Debian |
|---|---|
![]() |
![]() |
| Fedora | Bazzite |
|---|---|
![]() |
|:-:|
| ZorinOS | Ubuntu |
|---|---|
![]() |
Some of the best software ever made in my opinion:
- Linux and wine because they are impossible to create
- tcc, openrc, dwm, doas because clean, simple and readable code is the hardest code to make
- C because it was made by legends (and makes it simpler to write clean code)
- Rust because it actually made it simpler to write error-free code (not just about mem safety but also the code style and "spirit")
The perfect system is resilient and always up. Resistant to memory corruption via ECC and other technologies, resistant to power failures/spikes/brownouts via UPS and the likes, resitant to human tampering / unauthorized physical access, and resitant to human stupidity with High Availablitity VMs in redondant clusters and 3-2-1 backups. The perfect system only includes perfect software and therefore doesn't exist in real life.
The perfect code is both error-free and clean. Error-free which means bug-free, both logically (sound program logic) and physically (memory safety, resitant to external errors like no more disk space or internet and unexpected bugs). Clean means simple, easy to understand, and small in LoC while still respecting these two principles. Perfect software is feature-complete (and therefore "done") but also always funded and maintained security-wise. Therefore, perfect software is extremely rare.
I may be young but I am not a beginner, having over a decade of experience in linux systems and securing whole datacenters from the hardware to the end user. Able to learn new things fast and well if needed.
I don't use github often for my own projects (I don't trust microsoft to maintain a proper uptime) hence my rather empty account, I prefer to use self-hosted free software such as gogs.
If you read all this, have a nice day!





