Keepass 2.7.7 introduced support for Passkeys. This is controlled with the CMake build option WITH_XC_BROWSER_PASSKEYS. This is not handled in the ebuild. It can be enabled by users using the CMAKE compiler flag overrides, but I think it would make more sense to add it to the ebuild, as it's more expected behavior. It should probably follow the browser USE flag, but a separate USE flag could be added too. Reproducible: Always Steps to Reproduce: 1. Install KeepassXC 2.7.7 with browser USE flag enabled. 2. Configure browser support for KeepassXC and install the extension. 3. Enable Passkeys in the KeepassXC browser extension 4. Try to create a Passkey on a supported site. Actual Results: The browser will fall back to the native Passkey support (e.g. using a Yubikey). Expected Results: The KeepassXC Passkey prompt should come up.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=97686f9e0ce0b38208ae36443d3406728ad93ca6 commit 97686f9e0ce0b38208ae36443d3406728ad93ca6 Author: Maciej Barć <xgqt@gentoo.org> AuthorDate: 2024-03-12 16:06:57 +0000 Commit: Maciej Barć <xgqt@gentoo.org> CommitDate: 2024-03-12 17:03:36 +0000 app-admin/keepassxc: support browser passkeys Closes: https://bugs.gentoo.org/926837 Signed-off-by: Maciej Barć <xgqt@gentoo.org> .../keepassxc/{keepassxc-2.7.7-r1.ebuild => keepassxc-2.7.7-r2.ebuild} | 1 + 1 file changed, 1 insertion(+)
