YANEZ test partner
Local test partner for M3. It plays the partner website: it signs the session on its server and asks the YANEZ extension to start enrollment.
1 Extension
Checking…
Not found? Open chrome://extensions, turn on Developer mode,
choose Load unpacked and select extension/dist in the repo, then reload this page.
2 Optional: make the next backend answer fail (mock)
The real Yanez web route does not exist yet; a mock with the phone's contract answers. By default it answers normally (new YID, or the same YID for a duplicate face). A failure applies to the next enrollment only (the VM's 3 attempts), then answers are normal again.
3 Start enrollment
The extension opens its capture tab. The same user id + this browser = the same device binding (retries reuse its keys only if the face reproduces them).
S Sign with YANEZ (M4)
The partner server signs a phone-format request with its Ed25519 key and binds a purpose "sign" session to it. The extension shows the request before the camera opens; the VM signs and the reference RP verifier on this server checks the result.
"Send the last request again" replays the same request string under a fresh session: once it has been signed, the VM refuses it before the camera opens.
4 What happened (live)
Counts only. Helper records are encrypted inside the VM; this page never sees them.