Uwe Kögel

Had now some time to further look in into the issue and based on the logs I could find a possible fix for the issue which will be included in the next release.

Had now some time to further look in into the issue and based on the logs I could find a possible fix for the issue and which will be included in the next release.

Yes you can rename it and it will still be saved in that group. The group to save new passkeys is not identified by the group name, it identified by a static UUID.

yes you can rename, move or edit the group and passkey entries as you like. And there is a setting to prefer saving passkeys in the group selected in KeePass. For further deatils it might be worth checking the user guide https://keepasspasskey.github.io/docs/user-guide/#managing-passkeys-in-keepass

Thanks a lot for the log. I can confirm the issue: your laptop handles the Windows Hello part differently from most machines when saving a passkey, and that is what makes the save fail. I need to look into it a bit further, but I hope to fix the root cause in a future version. In the meantime there is a workaround that should let you save passkeys right now. Open the settings and find the verification option (there is one for Registration and one for Sign-in). Change it from "Both" (the default)...

Could you send me a bit more of the log so I can pin down the cause? In the app, look at the Provider.log tab, then copy the lines from around the moment you tried to save (a dozen lines before and after that "invalid RSA signature" warning is perfect). The whole block for that one save attempt is ideal. My guess is that your older hardware (i guess tpm 1.2) uses a different signature type that the plugin is not handling correctly yet, and the log might confirm it.

Just to make sure I understand: are you referring to the earlier problem where registering was not possible on your laptop (the TPM issue)? If so, glad it works now, and you did not miss anything in the changelog. The plugin did not change anything regarding TPM, so there is no changelog entry. I suspect the issue was on the Windows Hello side. Maybe a Windows update fixed it since, or it somehow self healed.

Thanks for the honest feedback. I agree, a password manager plugin should not be flagged as malicious software by an antivirus. Unfortunately this one got flagged by MS Defender. So on Tuesday, once I noticed there was an issue, I took it seriously and investigated. The full details are here: https://github.com/yusei36/KeePassPasskey/issues/20#issuecomment-4857704275 I submitted the files to Microsoft as false positives and they cleared the ones I sent, but clearance is per-file, so a new release...