n.Newfeed

Technology · 7 min read

How Passkeys Use Public-Key Signatures for Authentication

A step-by-step account of passkey registration, signed challenges, origin binding, synchronization, and recovery risks.

Registration creates a new credential

A passkey is not a password sent through a different form. It is a credential based on public-key cryptography and scoped to a particular online service. The service keeps a public key. An authenticator—often a phone, computer, password manager, or security key—controls the corresponding private key. During sign-in, the authenticator signs data about the request; the service verifies that signature.

The mechanism is implemented through WebAuthn, a World Wide Web Consortium specification, together with the FIDO protocols used between a client and an authenticator. “Passkey” is the product term commonly used for a discoverable WebAuthn credential: one that an authenticator can find for a service without the user typing a username first. Some passkeys are tied to one device; others are synchronized across a provider’s devices.

At registration, the website—called the relying party in the specification—asks the browser to create a credential. The request contains a fresh random challenge, the relying party identifier, account information, accepted algorithms, and preferences about authenticators and user verification. The browser checks that the calling web origin is allowed to claim that relying party identifier.

The authenticator creates a key pair after the user authorizes the action, commonly with a device PIN, fingerprint, or face check. It returns the public key, a credential identifier, and signed registration data. The private key does not go to the website. Depending on the product and policy, it remains inside secure device hardware, a software credential manager, or an end-to-end encrypted synchronization system.

The server stores what it needs to verify

The server associates the public key and credential identifier with the user account. It may also store a signature counter, transport hints, a credential name, and information needed for account management. None of those values can by itself produce a valid signature from the private key.

This is the first major difference from password authentication. A password verifier must be derived from a secret the user knows and submits. Competently built services store salted password hashes rather than plaintext, but a database breach can still enable offline guessing against weak passwords. With a passkey, the server database contains public verification material. Stealing it does not reveal the private key and does not create a secret that can be guessed offline in the same way.

Public does not mean unimportant. An attacker who changes a stored public key could redirect future authentication if the application also lets the attacker bind it to the victim’s account. Registration, recovery, session handling, and database integrity remain security-critical. Passkeys remove one class of shared-secret risk; they do not make the rest of the account system irrelevant.

Attestation is an optional part of registration that can provide information about the authenticator model or properties. Many consumer services avoid requiring identifying attestation because it can reduce privacy and interoperability. High-assurance organizations may use attestation to enforce device policy. The W3C specification deliberately gives relying parties choices because a bank, a public discussion board, and an enterprise administrator do not face the same threat model.

Authentication is a signed challenge

When a user returns, the service creates a new unpredictable challenge and sends it to the browser with the relying party identifier. The authenticator locates an eligible credential. The user selects an account if necessary and authorizes its use. “User presence” can mean a deliberate touch; “user verification” means the authenticator locally verified the person through a PIN or biometric mechanism.

The authenticator then signs a structured message. It includes the challenge through the client data, the relying party identifier through a cryptographic hash, flags recording user presence or verification, and other authenticator data. The server checks that the challenge matches the one it issued, that it has not expired or been reused, that the origin and relying party values are expected, and that the signature verifies under the registered public key.

The challenge prevents replay. A captured response is tied to one ceremony and cannot simply be submitted for a later challenge. The signature proves control of the private key without revealing that key. The origin and relying-party checks bind the ceremony to the intended service.

Biometrics play a narrower role than product screens sometimes imply. The website does not normally receive a fingerprint or face template. The local device uses its existing unlock mechanism to authorize the private-key operation, then reports whether user verification occurred. A passkey can also be protected by a device PIN. The cryptographic credential, not the biometric, is what the server verifies.

Origin binding changes the phishing problem

A convincing imitation of a password page can collect a password because the secret is typed into whatever page the user sees. WebAuthn credentials are scoped to a relying party identifier, usually a registrable domain. A passkey registered for example.com is not available to examp1e.com. The look-alike site can copy logos and words, but the browser and authenticator will not sign an assertion as if it came from the real domain.

This makes correctly deployed passkeys phishing-resistant in a stronger sense than one-time codes, which a reverse-proxy phishing site can relay in real time. NIST’s digital identity guidance classifies cryptographic authenticators using verifier-name binding as phishing-resistant. The W3C WebAuthn specification states the security claim with conditions: registration must be completed securely, the private key must remain confidential, and the relying party must validate the ceremony.

Those conditions expose the limits. If an attacker controls an authenticated session, corrupts account recovery, persuades support staff to enroll a new credential, or runs malicious code on the legitimate origin, origin binding does not restore the account. Cross-site scripting on the real service can initiate ceremonies in the correct origin, though it still faces user authorization and browser controls. Malware with sufficient control of an unlocked device can attack at other layers.

Synchronization and recovery move trust

Device-bound credentials provide a simple boundary: the private key stays on one authenticator. Losing that authenticator can also mean losing access unless another credential or recovery method exists. Synchronized passkeys improve availability by making credentials accessible on a user’s other devices through a credential provider.

Synchronization does not send the private key to the relying party, but it changes where protection must hold. Security now depends on the provider’s account controls, encryption design, device enrollment, and recovery process. FIDO distinguishes syncable and device-bound credentials because organizations may reasonably make different choices. A consumer service may prefer recovery and broad adoption; a high-assurance system may require hardware-bound credentials and tightly controlled enrollment.

Cross-device authentication provides another path. A person can use a nearby phone to approve sign-in on a computer, with the devices establishing a proximity-assisted channel and the phone using the passkey. The exact user experience varies across platforms. Confusing prompts or unexpected fallback paths can still lead users into unsafe actions even when the central cryptography is sound.

Services also need a transition strategy. If they leave password recovery unchanged and weak, an attacker may bypass the passkey. If they remove every fallback, users who lose devices may lose accounts. Mature deployments allow multiple authenticators, show credential-management activity, protect enrollment as carefully as login, and use recovery methods proportionate to the account’s value.

What passkeys establish—and what they do not

The established mechanism is specific. A passkey lets a service verify a fresh, origin-bound signature using a stored public key. The private key is not sent during registration or authentication, and a look-alike domain cannot request a signature for the legitimate relying party. These properties remove reusable passwords from the normal sign-in exchange and sharply reduce common credential-phishing and server-verifier theft risks.

Implementation details remain consequential. Synchronization can improve usability while broadening dependence on a platform account. Attestation can support device policy while reducing privacy. Recovery can preserve access while reopening a weaker route. Passkeys do not prevent session theft, application vulnerabilities, coerced device unlock, malicious account enrollment, or every form of social engineering.

The useful conclusion is therefore neither “passwords with nicer buttons” nor “authentication solved.” Passkeys replace a shared secret with a scoped cryptographic proof. That is a material security change. Whether the whole account is secure still depends on the registration, recovery, software, and human systems around the proof.

Sources and further reading

4 sources, 2 of them with a link you can follow.

  1. World Wide Web Consortium, Web Authentication: An API for Accessing Public Key Credentials—Level 3.
  2. FIDO Alliance, Client to Authenticator Protocol specifications and passkey technical resources.
  3. National Institute of Standards and Technology, Digital Identity Guidelines: Authentication and Authenticator Management, SP 800-63B.
  4. W3C WebAuthn Working Group and FIDO Alliance, implementation and security-considerations material accompanying the specifications.

Want the reader to remember this spot? Sign in — it is free.

Next How GPS Receivers Calculate Position from Satellite Time Signals

The app

Keep going, or take it with you.

Free accounts read twenty pieces a day. Pro is US$1.99 a month or US$11.99 a year for unlimited reading.