wellread1

I am correcting myself. The KeePassPasskey plugin https://keepass.info/plugins.html#kppasskey does make KeePass a passkey provider. The documentation for the plugin includes a block diagram at https://keepasspasskey.github.io/#how-it-works describing what roles the plugin and KeePass assume in the passkey creation and use process. Consequently it is correct to describe my reliance on a pure Windows implementation of passkeys as a preference. At the moment I don't see a compelling need to include...

I am correcting myself. The KeePassPasskey plugin https://keepass.info/plugins.html#kppasskey does make KeePass a passkey provider. The documentation for the plugin includes a block diagram at https://keepasspasskey.github.io/#how-it-works describing what roles the plugin and KeePass assume in the passkey creation and use process. Consequently it is correct to describe my reliance on a pure Windows implementation of passkeys as a preference. At the moment I don't see a compelling need to include...

No, I am saying that each passkey is created and managed by the OS and the site that you want to login to. A password manager can do nothing more than backup one side of the passkey. This backup is unnecessary because if the passkey gets corrupted all you have to do is create a new passkey using the same process that you used to create the first passkey for the site. When you use a passkey you are telling your OS to assert your identity to the website. The OS does this by using face recognition,...

No, I am saying that each passkey is created and managed by the OS and the site that you want to login to. A password manager can do nothing more than backup one side of the passkey. This backup is unnecessary because if the passkey gets corrupted all you have to do is create a new passkey using the same process that you used to create the first passkey for the site. When you use a passkey you are telling your OS to assert your identity to the website. The OS does this by using face recognition,...

No, I am saying that each passkey is created and managed by the OS and the site that you want to login to. A password manager can do nothing more than backup one side of the passkey. This backup is unnecessary because if the passkey gets corrupted all you have to do is create a new one using the same process that you used to create the first passkey for the site. When you use a passkey you are telling your OS to assert your identity to the website. The OS does this by using face recognition, finger...

No, I saying that each passkey is created and managed by the OS and the site that you want to login to. A password manager can do nothing more than backup one side of the passkey. This backup is unnecessary because if the passkey gets corrupted all you have to do is create a new one using the same process that you used to create the first passkey for the site. When you use a passkey you are telling your OS to assert your identity to the website. The OS does this by using face recognition, finger...

No, I saying that each passkey is created and managed by the OS and the site that you want to login to. A password manager can do nothing more than backup one side of the passkey. This backup is unnecessary because if the passkey gets corrupted all you have to do is create a new one using the same process that you used to create the first passkey for the site. When you use a passkey you are telling your OS to assert your identity to the website. The OS does this by using face recognition, finger...

You don't need to manage passkeys with KeePass. Currently passkeys are an alternate way to access a site account, they don't replace standard site credentials, e.g., usernames and passwords. They are a cryptographic key-pair typically managed by the OS acting as an ID authenticator and a particular site. Simply create the passkey when requested, then let the OS manage it. If you are concerned that the passkey will replace account credentials call Vanguard etc. and verify that a passkey won't replace...