SUMMARY Plasma-Vault is a brilliant tool that I use every day. It lacks one crucial feature. As far as I found it can't be operated with commands like opening/closing the vault. It is a security software. This basic feature will increase its usability. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.82.0 Qt Version: 5.15.2 Kernel Version: 5.12.9-arch1-1 OS Type: 64-bit Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6200U CPU @ 2.30GHz Memory: 3.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520
Seems reasonable.
I second this feature request. For example I think dealing with multiple Vaults can also be much easier this way. For example with a "close all" command etc.
Hi, There are two CLI-only commands that the Vault supports that were introduced for nice integration with KDE Connect [1]: qdbus org.kde.kded5 /modules/plasmavault closeAllVaults qdbus org.kde.kded5 /modules/plasmavault forceCloseAllVaults qdbus org.kde.kded5 /modules/plasmavault closeVault qdbus org.kde.kded5 /modules/plasmavault forceCloseVault Opening vaults from CLI is problematic. Communicating the password between the CLI command and the Vaults service would be insecure. This might be doable in a secure way if the CLI command cloned the whole logic of GUI Vaults, but this would need some non-password synchronization between different things that are allowed to open vaults. This would need to be thought through and will result in significant refactor / reimplementation. The good part of this potential refactor, if I manage to prove it doesn't open new vectors of attack, is that it would allow Plasma to show password fields inline in the Vault applet instead of them being shown in a separate window owned by a random process (KDED). I'll mark this as assigned. [1] https://cukic.co/2018/04/14/plasma-vault-with-kde-connect-and-more/
(In reply to Ivan Čukić from comment #3) > Hi, > > There are two CLI-only commands that the Vault supports that were introduced > for nice integration with KDE Connect [1]: > > qdbus org.kde.kded5 /modules/plasmavault closeAllVaults > qdbus org.kde.kded5 /modules/plasmavault forceCloseAllVaults > qdbus org.kde.kded5 /modules/plasmavault closeVault > qdbus org.kde.kded5 /modules/plasmavault forceCloseVault > > Opening vaults from CLI is problematic. Communicating the password between > the CLI command and the Vaults service would be insecure. This might be > doable in a secure way if the CLI command cloned the whole logic of GUI > Vaults, but this would need some non-password synchronization between > different things that are allowed to open vaults. This would need to be > thought through and will result in significant refactor / reimplementation. > > The good part of this potential refactor, if I manage to prove it doesn't > open new vectors of attack, is that it would allow Plasma to show password > fields inline in the Vault applet instead of them being shown in a separate > window owned by a random process (KDED). > > I'll mark this as assigned. > > [1] https://cukic.co/2018/04/14/plasma-vault-with-kde-connect-and-more/ Good to know (about the existing cli features) and thanks for assigning this.
Because the tool uses standard CLI commands under the hood, you can also interact with them directly. This is what I do when I need a CLI interface for interacting with my vaults. Unsure if we need anything extra IMO.