Opaque, Interoperable Passkey Records (and a Go API)
gnabgib
30 points
5 comments
July 20, 2026
Related Discussions
Found 5 related stories in 103.2ms across 9,963 title embeddings via pgvector HNSW
- I don't like passkeys ethanhawksley · 752 pts · September 18, 2026 · 51% similar
- Passkeys are a trap laurex · 455 pts · October 11, 2026 · 49% similar
- Show HN: Anonymous age verification with passkey-powered encryption mikeysight · 13 pts · August 19, 2026 · 48% similar
- Passkeys are not a trap speckx · 553 pts · October 14, 2026 · 47% similar
- Why I Still Shun Passkeys HotGarbage · 30 pts · October 16, 2026 · 47% similar
Discussion Highlights (2 comments)
cadamsdotcom
Ok so we are achieving interoperability by turning passkeys into strings. You know what it's called when you store a secret string in your password manager? A password.
deathanatos
From the linked spec, > The authenticator data is a CBOR structure defined in the WebAuthn Level 3 specification, is returned by the getAuthenticatorData() method of the AuthenticatorAttestationResponse From TFA, > The payload is the authenticator data, a CTAP2 CBOR encoding of most of the credential record fields that is already specified by WebAuthn Both link to the same section of the WebAuthn spec, §6.1 Authenticator Data[1]. Unless I'm missing something, that section is describing a custom binary format, not a CBOR encoding of data. (Though n.b. that one of the items contained by the outer custom binary format is CBOR, but the 37(ish) byte array itself is not CBOR.) (…and it's stuff like that that just makes all of WebAuthn so impenetrable.) [1]: https://www.w3.org/TR/webauthn-3/#sctn-authenticator-data