Documentation

Integrity at the boundary.

Frontera is a GNU/Linux anti-tamper stack: self-integrity, hypervisor guard, optional eBPF ptrace watching, plus MBA and rolling-key VM obfuscation for sensitive functions.

The intended consumer path is small: include the umbrella header, mark functions with[[frontera::protect]], build through cxx-frontera.sh or CMake so sources are rewritten and the binary is stamped, then ship. There is no separate policy file or remote report channel—checks run in-process and react locally.

Guides

• Getting startedProtect a function, build, stamp, and run the consumer pattern.
• Build & integrateLink flags, cxx-frontera.sh, CMake helpers, and what startup does.
• API referencefrontera_at, frontera.hpp, MBA, RKVM, and phomo surfaces.
• Protect & stampfrontera-protect, frontera-stamp, and digest-slot integrity.

What runs at startup

When antitamper is active, frontera_at_start() (directly or via a protected stub):

1. Verifies the stamped SHA-256 of the running binary against the embedded digest slot.
2. Establishes or checks an executable-memory baseline from /proc/self/maps.
3. Runs hypervisor detection and may hard-exit on high confidence.
4. Best-effort starts phomo’s eBPF ptrace watcher (soft-fails without CAP_BPF).