Boy I’m so tired of people trying to make clever attack names. They don’t help remember things, there are too many. So all 3 “pass-ta-key” attacks are not attacks on passkeys, they’re attacks on the Google vault. And if you get access to the vault, then you get everything. OK. And if you get access to a synced traditional password vault, then you get everything. So… meh. These are bugs, they will be fixed. Good on th…
Pass the Passkey: A Novel Attack Surface in Passwordless Authentication
11–20 of 54 posts
Re: Pass the Passkey: A Novel Attack Surface in Passwordless Authentication
#12Re: Pass the Passkey: A Novel Attack Surface in Passwordless Authentication
#13Boy I’m so tired of people trying to make clever attack names. They don’t help remember things, there are too many. So all 3 “pass-ta-key” attacks are not attacks on passkeys, they’re attacks on the Google vault. And if you get access to the vault, then you get everything. OK. And if you get access to a synced traditional password vault, then you get everything. So… meh. These are bugs, they will be fixed. Good on th…
Have we standardized a way to backup and export passkeys yet? Do websites commonly allow multiple passkeys to be registered?
To my understanding both Apple Passwords and the Android equivalent allow you to export passkeys to a different app (password manager), but I haven’t tried it yet.
If anyone has direct experience I appreciate to know how it was.
Re: Pass the Passkey: A Novel Attack Surface in Passwordless Authentication
#14Boy I’m so tired of people trying to make clever attack names. They don’t help remember things, there are too many. So all 3 “pass-ta-key” attacks are not attacks on passkeys, they’re attacks on the Google vault. And if you get access to the vault, then you get everything. OK. And if you get access to a synced traditional password vault, then you get everything. So… meh. These are bugs, they will be fixed. Good on th…
Have we standardized a way to backup and export passkeys yet? Do websites commonly allow multiple passkeys to be registered?
1. All sites/services would allow the registration of 5 or more keys, which can be tracked/revoked separately. That way if one device is stolen, you can invalidate that key without affecting others.
2. There are two sets of keys: "Regular Use" and "Backup/Recovery".
3. Attempting to use a Backup/Recovery key prompts to user to confirm that they want to invalidate the Regular keys and promote the backup key(s) to the new regular. In this way, a compromised backup cannot be used in secret.
Re: Pass the Passkey: A Novel Attack Surface in Passwordless Authentication
#15"You must enable DRM to play some audio or video on this page" pops up in the strangest places...
Re: Pass the Passkey: A Novel Attack Surface in Passwordless Authentication
#16Earlier quoted context omitted.
Have we standardized a way to backup and export passkeys yet? Do websites commonly allow multiple passkeys to be registered?
There’s FIDO CXF/CXP: https://fidoalliance.org/specs/cx/cxf-v1.0-ps-errata-2026030... To my understanding both Apple Passwords and the Android equivalent allow you to export passkeys to a different app (password manager), but I haven’t tried it yet. If anyone has direct experience I appreciate to know how it was.
Re: Pass the Passkey: A Novel Attack Surface in Passwordless Authentication
#17>4. Using the hash of that handshake, the attacker interacts with the victim’s TPM and uses the extracted identity key to sign the handshake hash together with the assertion request Huh? If you have this level of local privileges you can just read session cookies from the browsers store? I guess stealing all the keys is notable, but you can manipulate any password manager with this level of access right? What's the t…
I think that is the idea actually. By using secure hardware features it is in theory possible to secure the passkeys even in the case of compromised clients. Like how the iphone uses a security coprocessor to store the decryption keys and face id info out of the reach of iOS.
But this isn't overly concerning since it's still at a minimum as secure as passwords in a local compromise situation.
Re: Pass the Passkey: A Novel Attack Surface in Passwordless Authentication
#18Boy I’m so tired of people trying to make clever attack names. They don’t help remember things, there are too many. So all 3 “pass-ta-key” attacks are not attacks on passkeys, they’re attacks on the Google vault. And if you get access to the vault, then you get everything. OK. And if you get access to a synced traditional password vault, then you get everything. So… meh. These are bugs, they will be fixed. Good on th…
Have we standardized a way to backup and export passkeys yet? Do websites commonly allow multiple passkeys to be registered?
Re: Pass the Passkey: A Novel Attack Surface in Passwordless Authentication
#19Earlier quoted context omitted.
Have we standardized a way to backup and export passkeys yet? Do websites commonly allow multiple passkeys to be registered?
There’s FIDO CXF/CXP: https://fidoalliance.org/specs/cx/cxf-v1.0-ps-errata-2026030... To my understanding both Apple Passwords and the Android equivalent allow you to export passkeys to a different app (password manager), but I haven’t tried it yet. If anyone has direct experience I appreciate to know how it was.
Re: Pass the Passkey: A Novel Attack Surface in Passwordless Authentication
#20For example, it really ought to be possible to seal a secret such that it can only be unsealed if PCRs have certain values (the usual TPM thing) and the requester of the unseal operation is tagged by the OS (software TCB) as having a certain identity. The latter part is entirely missing from the TPM spec. (The identity could be a hash of the process, just a UUID, or just about anything else as long as it was reasonably well associated with the process in question. Obviously there are subtleties here.)
If the TPM worked the way I wanted, an unprivileged process running alongside Chrome would be completely unable to use the TPM to pretend to be Chrome.