https://bugs.kde.org/show_bug.cgi?id=385988

--- Comment #1 from Ivan Čukić <[email protected]> ---
Before I start - the Vault applet is made to look as much as the device applet
since they do similar things.

While I mostly like the proposed ideas, I'm afraid that most of them go into 
1) overly problematic to implement properly (I'm trying to keep things as
simple as possible because we had great ideas some years ago, but most of the
ideas required holes in security :) or 
2) It would be really cool to have, but I'm unsure a simple applet is the right
place for it.


Commenting in a changed order:

> 5: Create new vault

Yes, the button can be made flat as in the activity switcher

> 4: for the vault, show recently opened documents.

This is a cool idea, but I'm afraid it is out of the scope of the applet (and
would be really problematic implementation-wise).

The 'recent documents' meta-data is one of the privacy concerns I have with
Vaults. While the contents of a file is encrypted, the "Hey, you opened the
file named 'how-to-make-your-secret-lair.txt' in Kate" is not - and that can be
problematic. :)

> 2: when hovering anywhere on the encrypted vault or files (see 4)

I don't think that "configure" is an action that should be invoked often --
therefore, I do not see the reason to show it next to the mount/umount.

> 1: The 'name' is obviously the name of the vault, but when 
> hovering over it you see it is clickable. Clicking it will open the directory 
> in dolphin.

This I would be fine with, if that was how the Device notifier would behave.

One thing where the Device notifier UI beats Vault is that it automatically
expands the actions for the last inserted device. I'm not sure what that would
mean for vaults.

> 6: opened, here it slides out an input field for the password and an Ok 
> button to attempt mounting it.

This is something I'm investigating. If I manage to do it in a secure way
(without Plasma sending the password to the Vault daemon via dbus or other
channel that can be spied on), this will be implemented.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to