IN DUBIO NEGA
OGOPSEC · Authorization-State Guardian · Tier II · Preparing for launch

A USB credential anchored in your machine's own hardware.

Turn a compatible USB stick into an encrypted vault and a login credential — with TPM-backed clone and rollback detection, locked to the computer you choose and minted on an offline machine. No cloud. No account. Your passphrase is never transmitted to OGOPSEC. The stick is ordinary on purpose. The wolf is the software.

One-time license·Node-locked to your machine·30-day guarantee
Your stick, your machineNo cloud, no account Public, vetted cryptoAir-gapped enrollment
recovery.log — provisioning ceremony (air-gapped)live build
  DIRE WOLF . RECOVERY   (air-gapped)
[proof] net ifaces: lo              (refuses to run if a network exists)
[recovery] stick: /dev/sdb   vault partition: /dev/sdb2
[recovery] main machine pre-bind: auto-read from the stick
[recovery] sealing opaque vault onto P2 ...
[recovery] ✅ VAULT SEALED AND VERIFIED

$ unlock --tpm
  STATUS: AUTHORIZED   anchor: TPM   counter_used: 931 → 932
  a rolled-back or cloned copy: CLONE_SUSPECTED

What most "secure USB" tools quietly get wrong

Encryption is the easy part. The hard part is proving a stick is the real one, on the right machine, and not an old copy.

I

Lose it, lose everything

One encrypted stick, no recovery path. A single failure and the data is gone for good.

II

A copy they can't detect

Byte-copy the stick and both work. Nothing on the device notices it was cloned.

III

Rollback you can't see

Restore an old image and the "latest" credential silently reverts. No alarm, no trace.

IV

"Trust us, it's encrypted"

Closed, secret internals you're asked to believe in. Security that leans on secrecy isn't security.

What Dire Wolf is — and what it isn't

We tell you exactly what it protects against and where the line is. That honesty is the product.

✓ What it is

  • ✓An encrypted vault (ChaCha20-Poly1305, Argon2id / scrypt) on a compatible USB stick you provide.
  • ✓A credential bound to your machine and verified against its TPM.
  • ✓TPM-backed clone and rollback detection via a hardware monotonic counter.
  • ✓Minted air-gapped — the enrollment OS refuses to run on a networked machine.
  • ✓Yours. The passphrase lives in your memory; no vendor can recover or reset it.

✕ What it is not

  • ✕Not unbreakable. No credential is. We publish the limits in full.
  • ✕Not a cloud service, not an account, not a subscription.
  • ✕Not recoverable if you forget the passphrase — that is the point.
  • ✕Not proof against someone who has both your stick and your passphrase — that threat needs Tier III hardware.
  • ✕Not security-by-secrecy. The method is public; only your passphrase is secret.

How it works, in three steps

Set it up on your machine, mint it offline, then unlock. The dangerous steps are deliberately separated.

Step 01 · Main machine

Set up the stick

One command formats your USB, writes a signed recovery system to it, and records which machine it belongs to.

$ direwolf setup /dev/sdb
  ✅ recovery flashed · signed
  ✅ machine fingerprint written
Step 02 · Offline

Mint it air-gapped

Boot the stick on an offline machine. It verifies there is no network, then seals your encrypted vault where no one can reach it.

[proof] net ifaces: lo
  ✅ VAULT SEALED AND VERIFIED
Step 03 · Every day

Unlock

Plug in, enter your passphrase. The credential authorizes and the hardware counter steps forward — an old or cloned copy is rejected on sight.

  STATUS: AUTHORIZED
  anchor: TPM · counter 931 → 932

Will it work for you?

Dire Wolf uses hardware you almost certainly already have. You bring the stick.

▣
A TPM 2.0 — built into modern machines

AMD fTPM and Intel PTT ship enabled on most PCs from the last several years. No add-on token to buy. Verified on AMD Ryzen + MSI B550.

⌁
Linux

Verified on Linux Mint. The container format is OS-agnostic by design; broader platform support is on the roadmap.

⊏
A compatible USB flash drive

The stick is just storage — the value and the anchor live in the software and your machine's TPM. Supported-drive requirements are published as compatibility testing completes.

◉
A passphrase you can remember

Generated for you with real entropy, or bring your own through a strict strength check. It is never written to the stick.

The tier ladder

Each rung up asks more of the hardware. Dire Wolf ships at Tier II.

III
Secure element / FIPS

A non-exportable key in dedicated hardware — clone prevention, not only detection, and a FIPS-track path for government and compliance buyers. In development.

II
TPM-anchored Ships here

Your machine's TPM holds a hardware monotonic counter the software cannot roll back. A stale or cloned copy presents an old counter and is rejected. This is the flagship.

I
Software file-store

A software-only anchor that detects concurrent clones but can be rolled back by restoring old files. Superseded by Tier II.

Why this exists

The security is public, vetted cryptography — not secret code.
Principle · Kerckhoffs
We publish what it protects, and what it does not.
Principle · Honest limits
Every claim is reproducible. We keep the receipts.
Principle · Evidence
Private evaluation program

Think you can break the Wolf?

We invite security researchers to attack Dire Wolf under a signed agreement: test it for up to 30 days, report privately, and publish your findings once we have had a chance to fix and credit you. The method is public — see if the hardware holds. Wolf may growl under adversarial conditions.

Apply to the program

Get Dire Wolf

One-time license, locked to one machine. Tier II is the flagship; Tier III hardware is in development.

● Flagship · preparing for launch

Tier II — TPM Anchored

$— / one-time · per machine
  • Encrypted vault on your own USB
  • TPM-backed, rollback-aware clone detection
  • Air-gapped enrollment ceremony
  • Node-locked license · 30-day guarantee
  • Instant download · no account
Join the launch list
◇ In development

Tier III — Secure Element

Coming / when it's real, not before
  • Non-exportable key in dedicated hardware
  • Clone prevention, not only detection
  • FIPS-track for compliance buyers
  • For the threat Tier II honestly can't cover
Follow development

Direct answers

Is my data ever sent anywhere?

The product has no cloud, no account, and no telemetry — everything happens on your machine and your stick, and enrollment runs offline and refuses to continue if it detects a network. Buying a license is a separate, ordinary purchase: your email receives the key, which is billing information, not product data.

What if I lose the stick?

A lost or stolen stick is useless without your passphrase — the vault is encrypted. For continuity you provision a second stick of your own; recovery is built around a memorized passphrase, with no written secret to steal.

What if I forget the passphrase?

Then the vault stays sealed — by design. There is no vendor backdoor and no reset. We help you generate a strong passphrase you can actually remember, and recommend provisioning a backup stick while you still have access.

Can't someone just copy the stick?

They can copy the bytes, but the copy is detected. Each unlock steps a monotonic counter anchored in your machine's TPM, which the software cannot move backward. An old or cloned copy presents a stale counter and is rejected.

Why keep the source closed if you believe in open crypto?

The security does not depend on secret code — it uses public, standard primitives. What we protect is the product, not the method. Researchers can attack the binary fully under our evaluation program, and we publish honest limits rather than hiding them.

What happens after I buy?

You get an instant download and a license key by email. The license is tied to one machine's fingerprint; it will not activate a second machine without a second license.