Attacks · Overview

Attack conversion

Most attacks succeed by turning something you can see or steal into something you can use. One-shot proofs break that conversion: surface observations need not become secret knowledge, and spent nonces cannot return as authority.

~7 min readContinue: Attack map

What the attacker wants

The attacker’s job is almost never “break math for sport.” It is conversion: take a transcript, a stolen token, a vault dump, a relayed ceremony fragment, or a mutated request and turn that capture into usable request authority. Classical deployments make that step cheap. If possession is authority, then seeing or stealing something is already most of the win - the rest is packaging the secret as a caller. Every family in this catalog argues whether that conversion still pays. Read each family page as a specialized conversion path: different capture surfaces, same question - does capture become lasting authority?

How it works today

In the ambient world the conversion works by design. Bearer tokens authorize until expiry. API keys work from any host that holds them. Passwords and OTPs are strings you can type again. Session cookies follow the browser. Vaults, agents, and CI runners amplify blast radius because the same object that authenticates also travels. Capture and reuse are the same game: surface bits become lasting callers. That is why vault dumps, phished OTPs, and replayed bearer tokens feel like the same incident class in postmortems.

Why it fails against one-shot proofs

ENI6MA aims to break the conversion step itself. Under empty effective channel design, notebooks can fill with surface bits while effective mutual information with the secret stays empty under the named model. Request-bound envelopes and burn-before-validate then deny reuse even when an observer records every visible step. Seeing or stealing something is not the same as owning lasting authority. The plates below show the ambient conversion path and the denial stack - empty effective bits, spent nonces, and binding - that make family-level attacks fail to cash out. Absolute claims stay model-scoped to the reference architecture.

Capture surfaces converting transcript, token dump, and relayed proof into usable authority — See or steal → use
How to read: left capture surfaces feed defined conversion steps; right ambient win shows authority gained. Takeaway: classical attacks pay at the conversion step.

That left-to-right path is how classical breaches pay: capture surfaces feed a conversion step, and the conversion prints lasting authority. If conversion succeeds, every downstream family is just a different capture surface.

Cracked conversion path with empty effective bits, spent nonce, and binding hold — Attack conversion fails
How to read: left conversion myths crossed out; right denial stack (empty MI, burn, binding). Takeaway: surface fills notebooks; authority does not transfer.

When conversion fails, the rest of the catalog becomes mechanism detail - which check denies which capture surface - not a promise that nothing bad can ever be observed. Surface notebooks may still fill; the question is whether those surface bits become effective bits against the secret.

Authority expires at the end of each request.ShippingThe envelope binds method, endpoint_id, request hash, policy hash, tau, and nonce (one message, one use).Holds under the reference architecture

Every envelope is bound to a specific method, endpoint, request body, policy, freshness window, and nonce.Shippingsha256(method || endpoint_id || request_body_hash || policy_hash || tau || nonce_uuid)Holds under the reference architecture

Where it shows up

APIs & workloads
Stolen API keys become lasting callers - conversion is the whole breach path.
Agents & MCP
Tool secrets that survive clone/copy convert into blast radius.
Human authentication
Harvested passwords and OTPs are reusable credentials by design.

Watch it fail

Run VerifyFalsify allow and replay paths against a live gate.
Prove it checklist

Go deeper

Why classical attacks failTheory summary of conversion denial.
Channel ZeroEmpty effective channel framing.

Why Naive Attack Intuition Is Wrong
Written for challengers who worry that watching multiple successful logins reveals the password and private map, or that random guessing eventually hits both, this essay explains why those paths do not work for the ENI6MA rotating-ring method (not mathematically, statistically, computationally, or physically).
Toward Perfect Secrecy by Design
This paper presents an end-to-end security argument for an ENI6MA-style interactive proof in which the attacker gains nothing in Shannon’s sense of perfect secrecy. The mechanism combines a one-time, entropy-dependent projection of the alphabet into six perceptual leaves; ring-rotation diffusion that spreads symbol appearances across a large configuration space; confusion from a private bijective map to six synonyms; and a second-layer enumeration of the 6! leaf permutations.
The Observer's Bit Budget in a Full Rosario Cipher Interaction
A quantitative information-theoretic analysis of how much an adversary can learn by observing a complete ENI6MA / Rosario–Wang authentication ceremony. The paper separates surface bits (Shannon entropy of symbols an observer can record) from effective bits (secret-relevant mutual information those recordings pin down), and argues that effective mutual information with the secret remains zero across rounds and ceremonies under the named model.

Formal note

Conversion denial is the visitor catalog frame for empty effective mutual information plus one-shot request authority: an observer may record surface bits while I_effective with the secret stays empty under the named model, and burned envelopes cannot return as lasting callers. Absolute claims remain model-scoped to the reference architecture. Go deeper via naive-attack-intuition and observer-bit papers for surface-versus-effective and residue framing.

Opening