Skip to content

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

@StayPirate

Description

@StayPirate

I initially reported this issue to flathub/org.keepassxc.KeePassXC#109, but maybe this place is more appropriate as the behave seems to be related to KPXC in general and not to its flatpaked version.


The problem of fingerprinting short-live processes was lengthy discussed #7571 and #6458. The quickest workaround is to set ConfirmAccessItem=false under [FdoSecrets] to revert to 2.6.x behavior.

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 I'm using KPXC installed via flatpak and nextcloud-client too. My best guess is that KPXC has no visibility over the nextcloud binary because it's from another flatpak container.

Acceptance criteria

When ConfirmAccessItem is set to false KPXC shouldn't show the "Requesting access" dialog, regardless if it can access the client binary or not.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions