Question: about the kv-store

[ObiWahn]

Hi,I have read the post and I understand the frustration with d-bus.

Is this store just meant as some sort of service that allows apps to save their secrets in a secure location. So not every app has to invent a store again?

This somehow sounds like a total lockdown. And I wonder how you want to authenticate the applications. Ok I put like 5 different passwords in my pc when starting, but most people will probably prefer to have just one.
To be really better I think the there must be some way for the applications to prove their identity. And if this is solved there can be filtering. Like apps x,y,z may use secrets of category 1 and 2 but not 3. The browser may share screen dp-1 but not the window of the password manager that is currently on screen.
And tooling to show what actually goes on would be nice as well. Something that hides the binary garbage of notification images and so on. When I looked at what is send over d-bus I wanted to tear my eyes out and cry. To have fix types with a short representation, that can be expanded at will would be super awesome.

[vaxerski]

For un-sandboxed apps, this is impossible. We do the best we can, but ultimately LD_PRELOAD, compromised libraries, and other loopholes will exist.

For sandboxed apps, kv is restricted to the app and we can verify it. For flatpak for example, each app has an exported FLATPAK_ID.

Currently the store has two key types:

• unbounded: all apps can read the secret as long as they know its name
• app: only the caller can read it