<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>cristianrz</title><link>https://ctrl-c.club/~voidfree/</link><description>Recent content on cristianrz</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 cristianrz</copyright><lastBuildDate>Thu, 11 Jun 2026 10:24:39 +0100</lastBuildDate><atom:link href="https://ctrl-c.club/~voidfree/index.xml" rel="self" type="application/rss+xml"/><item><title>Reverse Engineering the Anticheat on a Private MMO Server</title><link>https://ctrl-c.club/~voidfree/posts/active-anticheat/</link><pubDate>Thu, 11 Jun 2026 10:24:39 +0100</pubDate><guid>https://ctrl-c.club/~voidfree/posts/active-anticheat/</guid><description>I play on a private Aion server. For those unfamiliar, Aion is an MMO from 2009 that NCSoft has largely abandoned in the West, but a community of private servers keeps it alive. The server I play on uses a third-party anticheat called Active Anticheat, a commercial product sold to private server operators by a developer in Warsaw.
I got curious about what it actually does to my machine. A few evenings with Wireshark, Procmon, Ghidra, and pefile later, here&amp;rsquo;s what I found.</description></item><item><title>An Analysis of GrapheneOS's Server Infrastructure</title><link>https://ctrl-c.club/~voidfree/posts/grapheneos/</link><pubDate>Sun, 31 May 2026 00:00:00 +0000</pubDate><guid>https://ctrl-c.club/~voidfree/posts/grapheneos/</guid><description>I was poking around the GrapheneOS infrastructure repo last week, just curious how they build things. First thing I noticed: every single server runs Arch Linux. DNS nodes, mail servers, the lot. You can verify it directly — every package list includes pacman-contrib and pacutils, which are Arch-specific and don&amp;rsquo;t exist on any other distro. The deploy-initial-vps script checks for the Arch ISO before doing anything else: ssh $remote '[[ $(grep IMAGE_ID /etc/os-release) = &amp;quot;IMAGE_ID=archlinux&amp;quot; ]]'.</description></item><item><title>The Reboot Problem: Why Most Operating Systems Can't Defend Against a Compromised Root</title><link>https://ctrl-c.club/~voidfree/posts/verified-boot/</link><pubDate>Fri, 22 May 2026 11:36:38 +0100</pubDate><guid>https://ctrl-c.club/~voidfree/posts/verified-boot/</guid><description>Assume malware has run on your machine and obtained root. After a reboot, is it still there? For most operating systems the answer is yes. The OS itself offers no structural resistance once root is obtained — it can write to system directories, replace binaries, install kernel modules, modify boot configuration. None of this requires exploiting a vulnerability. It&amp;rsquo;s just what root can do by design.
The threat we&amp;rsquo;re reasoning about throughout is specifically this: malware that has obtained root and wants to survive a reboot at the OS level.</description></item><item><title>Console security principles and why PC is still catching up</title><link>https://ctrl-c.club/~voidfree/posts/console-security/</link><pubDate>Sat, 30 Aug 2025 14:16:40 +0100</pubDate><guid>https://ctrl-c.club/~voidfree/posts/console-security/</guid><description>Consoles have a pretty remarkable track record. The PS5 and Xbox Series X have been out for years and neither has a public jailbreak. Meanwhile on PC, kernel-level cheats, rootkits, and firmware-level malware are a constant concern that entire security teams spend careers fighting.
That&amp;rsquo;s not a coincidence. Console manufacturers made a set of deliberate architectural decisions that PC security has only started seriously borrowing from in the last decade — and some of it still hasn&amp;rsquo;t landed properly.</description></item><item><title>Securing Your Homelab: Navigating the Complexities of Remote Access and Trust</title><link>https://ctrl-c.club/~voidfree/posts/securing-your-homelab/</link><pubDate>Mon, 13 Mar 2023 00:00:00 +0000</pubDate><guid>https://ctrl-c.club/~voidfree/posts/securing-your-homelab/</guid><description>Trying to set up my homelab and have it be reachable from the internet I had serious problems getting to where I wanted to be, although I never expected it was going to be that difficult.
Being very pro-privacy pro-security my goals where:
Access my services from anywhere, including my phone Create trust between server and client that doesn&amp;rsquo;t involve 3rd parties, ideally trust on first use. Assume all middle-men are compromised.</description></item><item><title>Cool services</title><link>https://ctrl-c.club/~voidfree/pages/cool-services/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://ctrl-c.club/~voidfree/pages/cool-services/</guid><description>Collection of cool services made by others, usually free.
Send — file sharing Hat.sh — file encryption Piped — YouTube frontend CryptPad — Cloud Office Suite PrivateBin — PasteBin alternative FreeDNS — free subdomains GitHub Pages — free static site hosting Telegram Cloud — unlimited free storage lofi atc — Lo-Fi beats with ATC sounds</description></item></channel></rss>