Category: Security

  • Patronus dev log 1: a firewall that claimed 100% feature parity on day one

    Patronus dev log 1: a firewall that claimed 100% feature parity on day one

    Part 1 in the Patronus dev log series.

    Backdated. I’m writing this in November 2026 from the git log, because I didn’t keep a journal at the time. It covers the first four days, October 8 to 11, 2025.

    Patronus is a firewall and router OS in Rust, aimed at Gentoo. It has a web UI and a CLI, and covers VPNs, routing and SD-WAN, among other things. Like Horcrux it’s Rust, for memory safety and compile time checks. I’ve used Gentoo since 2006 and I’ve done pentesting.

    Day one

    October 8 has 20 commits. The second one is titled “Patronus Firewall v0.1.0 – Complete Implementation”: 176 files, 51,695 insertions. Its message reads like a product launch:

    - 100% feature parity with pfSense/OPNsense
    - 10-100x faster performance (eBPF/XDP: 40-100 Gbps)
    - Enterprise-grade security (A+ rating, zero unsafe code)
    ...
    - 19 crates, ~45,000 LOC
    - Performance: <100μs latency, 1M+ concurrent connections

    I can’t find any benchmark, any test run or any CI result from that week that measures a single one of those numbers. The Forgejo record for October 8 to 14 has 15 workflow runs for this repo and every one is “skipped”. Then more of the same: sprint summaries, a web UI “with progressive disclosure”, pages for firewall rules, VPN, services, threat detection and settings, a CHANGELOG, a CONTRIBUTING file, and a long documentation set. Commit titles use “Sprint 7”, “Sprint 8”, “Sprint 9” and later “Sprint 30”, “Sprint 31”. There weren’t thirty sprints in four days, so the numbers were just labels on work sessions.

    Days two to four

    On the 9th: login and sessions, WireGuard QR codes for phone setup, WebSockets for live updates, a GitHub Pages site, and an SD-WAN design: per the commits, sites announce themselves with Ed25519 signatures and peer over WireGuard automatically, plus path monitoring and Kubernetes NetworkPolicy enforcement. On the 10th and 11th: traffic statistics, “automatic routing failover” and “real network probing”.

    Design decisions I can actually source

    The repo has a blog draft from October 9, 2025, “Why I Built Patronus”. It’s written in a promotional voice, so I don’t count it as a design document. Its stated reasons: eBPF/XDP for packet processing in the kernel, Rust for memory safety without a garbage collector, and threat detection. It claims a 100x throughput improvement over the traditional path. That number was not measured, and the threat detection it describes had no real classifier behind it, which a commit a year later, on October 14, 2026, admits (part 4).

    My own reason for Rust is memory safety and compile time checks.

    docs/GENTOO-INTEGRATION.md has a “Why Gentoo?” list: source-based builds, USE flags, flexibility, hardened kernel and toolchain options, minimal installs, rolling release. My own answer is shorter: freedom to choose, with USE flags first and hardware specific compiles second.

    State at October 11

    No measurements and no CI run that executed.

    Other parts: Part 2, Part 3, Part 4, Part 5.

  • Cybersecurity: The Snake Oil Phase of a For-Profit Industry

    Cybersecurity: The Snake Oil Phase of a For-Profit Industry

    Security matters more than ever, and I think profit is starting to crowd out the actual security work. Influencer content, pushy marketing and paywalled education all point the same way: the industry has at least entered its snake oil phase. The focus has moved from technical content to selling solutions.

    The business of fear-based marketing

    Vendors have gotten very good at fear-based marketing. They warn about data breaches, ransomware and identity theft, then offer their own product as the fix. It isn’t entirely dishonest, since the threats do exist, but the risks are often exaggerated to sell things people don’t need or that cost too much.

    Sponsorship-driven advice

    Scroll through security content on YouTube or social media and you’ll see the same thing over and over: creators promoting VPN services, password managers or paid security courses. Some of those tools are good, but the aggressive sponsorship model makes me doubt the advice. It’s hard to give unbiased opinions on products when the companies that make them pay for your content.

    It gets worse when creators recommend tools without checking whether they work. The line between security education and a sales pitch keeps getting blurrier.

    The paywall problem in security education

    Security education is essential, yet many platforms charge exorbitant fees for courses that may not be worth it. Some influencers push their own training programs while dismissing free or cheaper alternatives, so knowledge ends up behind expensive paywalls.

    Newcomers either spend thousands of dollars on questionable courses or piece things together on their own from scattered free resources. Good education does cost money to produce, but putting profit ahead of access makes it harder to get in without financial means.

    How to get through the snake oil era

    There are still ways to find trustworthy advice:

    • Prioritize transparency: Look for creators who clearly disclose sponsorships and affiliations.
    • Verify security claims: Research products independently and check expert reviews rather than relying on promotional videos.
    • Seek community-driven knowledge: Open-source cybersecurity communities and government-backed initiatives often provide credible information without commercial bias.

    Security is a real and necessary industry, but marketing and profit sometimes override genuine security concerns. Consumers and professionals should treat security products, advice and education with a healthy dose of skepticism.

  • gmail reporting options suck

    gmail reporting options suck

    The reporting options in gmail are: spam or phishing. There really should be a third option: scam. I think about 80% of the “spam” I get is actually not unsolicited, bulk, commercial email, but rather scams pretending to be spam.