Verify a binary built with the Executor

  1. Keep the public key

    oee keygen writes the private signing key oee.key, which oee build --sign-key uses, and the public verification key oee.pub.

  2. Inspect the binary

    Run oee inspect <binary> --verify-key oee.pub on the binary you received or built.

  3. Read the result

    It verifies the OEE! footer, the BLAKE3 Merkle root and the Ed25519 signature, and prints the embedded policy summary, the target OS and architecture and the bundled runtime versions.

Terminal
oee inspect ./dist/my-service --verify-key ./certs/oee.pub

What is verified

  • The fixed 128-byte OEE! footer: the segment offsets and sizes, the magic trailer and the schema version.
  • A 32-byte BLAKE3 Merkle root across the four segments before the footer: the supervisor, the signed policy, the runtime archive and the application bundle.
  • A 64-byte Ed25519 detached signature, checked against your public key.
  • The supervisor runs the same verification before the application starts: any byte modification to the supervisor, the embedded oee.yaml policy or the bundled runtime archive fails it, and the application never runs.

Verify the command-line tool

Verification details for the oee command-line tool are published with the release, beside its builds for each target.

Security reports

Security reports go to hello@openeng.ai.

Early preview — message us for access

Executor 1.0.0 is in early preview. Install it with one command, or write to us for a platform that has no build yet.