| Summary: | Distinguish between different operations on the wallet (like reading keys, adding keys, testing integration, etc) | ||
|---|---|---|---|
| Product: | [Applications] kwalletmanager | Reporter: | myndstream |
| Component: | general | Assignee: | Valentin Rusu <valir> |
| Status: | RESOLVED NOT A BUG | ||
| Severity: | task | CC: | fella, mk.mateng |
| Priority: | NOR | ||
| Version First Reported In: | 20.12.2 | ||
| Target Milestone: | --- | ||
| Platform: | Debian stable | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
myndstream
2022-01-13 12:40:54 UTC
Related to Bug 451039, but more granular. This would need access control for each API method (or group of methods), which can quickly get too confusing for most users (and annoying, if they'll need to Allow/Deny too often). KWallet's security model - or rather, the security model of the traditional, non-sandboxed linux system - doesn't really support allow us to do this in a reliable, safe way. With sandboxed apps and portals it will be possible to do a better job here, but then we're not looking at the kwallet API anymore anyway. |