Your evaluator session
- Evaluator
- Access level
- Code valid until
- Terms accepted
- version (read them)
What this evaluation covers
You can verify that only a hardware security key whose attestation chains to the Yubico root
can enroll; that PIN and touch are required here; that an agent certificate is issued only for a key the agent
holds (the server never makes agent keys); that registrations go to the c=US or c=CA tree you choose, under
ou=Evaluation; and that relying parties (agents.cequs.com and the sugarbushagent.com edges) honour C=US's
decision, including a refusal.
Your progress
- Access code accepted
- Security key set up (PIN and touch)
- Logged in (PIN and touch)
- Test agent registered
- Listing verified in the transparency log
Step 1 of 2 — Set up your security key
Watch for a pop-up window. Each time you click, a Windows Security window opens; it can open behind this browser. Enter the key's PIN (if it has none yet, create one), then touch the key when it blinks.
As on your access request. The code is bound to this account and to the first key you set up.
Step 2 of 2 — Log in
Same name as above; enter the PIN and touch the key again when it blinks.
Add a second key (recommended). If you lose your key or forget its PIN, your second key still works. Plug it in instead of the first, then click the button.
Lost both keys, or locked them with wrong PINs? Ask the C=US administrator for a new access code.
Register a test agent
By default this browser makes the agent's key and keeps it. To test with a key on your own device (a TPM or a hardware key), choose the certificate request file it made; you then get the certificate, never a key, to call agents.cequs.com and the sugarbushagent.com edges as a peer.
Records (elevated access)
The evaluation branch's issuance records and the evaluator session log, as the server keeps them. Reading them is logged.