Oh awesome I had seen the Fedora Magazine article but not the framework guide. I’ll give that a shot, thank you!

I did not, looking at my new laptop that file doesn’t even exist, is that something I can just create and add in to folder? On my current computer it exists, so I have a template at the very least.

No, I’m using UEFI so from what I read on the ArchWiki that’s only needed for older non-UEFI systems

You know I’m not 100% sure, I was following another tutorial that I can’t find anymore, but if I remember right 1 was for the UEFI state, 4 was to make sure the bootloader wasn’t changed, 5 was for secure boot, and 7 was for the OS being booted (To make sure someone isn’t booting Kali in a live disk or something), but I could be wrong.

Completed! Looking forward to seeing the results

Does amnezia work? Its obfuscated wireguard and is, according to their github, resistant to deep packet inspection and such

Julia Evans has such great and accessible content, they’re awesome

Looks like they put in a ton of effort to make this compatible with generic devices, but I have to ask, with all the features removed, why choose this over any other ROM?

Features removed

hardened_malloc — causes boot loops on devices with 39-bit virtual address space. replaced with AOSP Scudo.

Auditor — requires hardware attestation which > doesn’t work on GSI

mtectrl / misctrl — Pixel-specific memory tagging control; breaks vendor TEE drivers

USB protection — the low-level USB port controls rely on Pixel-specific hardware and are non-functional on other devices

native debugging protection — not ported; breaks compatibility with root solutions and vendor debugging tools

Features disabled by default

These can be re-enabled in TrebleApp → Hardening or Settings → Exploit protection.

MTE/TBI for vendor processes — memory tagging breaks some vendor drivers

hardened thread stacks — non-standard memory layout breaks some vendor drivers

secure (exec-based) app spawning — breaks root solutions (Magisk / KernelSU)