search

flathub / org.keepassxc.KeePassXC

https://flathub.org/apps/details/org.keepassxc.KeePassXC
27 stars 16 forks source link

KPXC doesn't honor ConfirmAccessItem in [FdoSecrets] when it cannot find the executable path #109

Closed StayPirate closed 1 year ago

StayPirate commented 1 year ago

The problem of fingerprinting short-live processes was lengthy discussed https://github.com/keepassxreboot/keepassxc/issues/7571 and https://github.com/keepassxreboot/keepassxc/issues/6458. The quickest workaround is to set ConfirmAccessItem=false under [FdoSecrets] to revert to 2.6.x behavior.

Flatpaked KPXC does not honor the ConfirmAccessItem option and keep showing the following dialog every time Nextcloud-client starts, even though I have ConfirmAccessItem=false

image

Please note that nextcloud-client is installed via Flatpak as well. I have no memories of this weird behavior in my previous setup where both KPXC and Nextcluoud-client where installed via the distro's packet manager.

StayPirate commented 1 year ago

My best guess is that KPXC has no visibility over the nextcloud binary because it's from another flatpak container. Hence, it behaves like shown above.

IMO if ConfirmAccessItem is set to false KPXC should not show that dialog, instead allows the process (with the inaccessible binary) to access the requested data right away.

droidmonkey commented 1 year ago

This is a bug in KeePassXC itself