|
|
|
|
|
by ganbatekudasai
1295 days ago
|
|
If that is ever the case, which I honestly think is doubtful (though I could be wrong), given that it's an open standard, I don't think there's anything preventing people from writing a passkey implementation that saves the secret key material in a plain file or anything similar. It likely already exists. |
|
Looking at KeepassXC's WebAuthn WIP implementation, it works by injecting JS into the website context that overrides the default JS API to its own implementation instead. [2] I don't see any API in the chrome extensions docs [3] that could be used to customize passkeys, so I assume 1Password's passkey implementation (mentioned in other comments in this thread) does the same thing. I sure hope the browsers don't decide to crack down on it by making the API uninterceptable in the name of security.
[1]: https://web.dev/passkey-registration/#call-webauthn-api-to-c...
[2]: https://github.com/keepassxreboot/keepassxc-browser/commit/4...
[3]: https://developer.chrome.com/docs/extensions/reference/