https://bugs.kde.org/show_bug.cgi?id=396334
Bug ID: 396334
Summary: Unencrypt data to same folder that vault encrypted
data is located
Product: Plasma Vault
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: wishlist
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
At now Plasma Vault store encrypted data in specific folder (by default at
~/.local/share/plasma-vault/vaultname.enc/ and can be changed in CryFS backend,
in EncFS data storage location can be changed via GUI).
But when user opens the vault - it mounts to another location at
~/Vault/vaultname folder.
This is confusing for new users, because when they close the vault - they see
empty directory and don't understand where is his files?
Use case: User configure Dropbox sync at ~/Dropbox folder, and want to encrypt
some folder. Via Plasma Vault it creates new vault with mountpoint
~/Dropbox/MyPrivateData, opens it and copy files to it. And after this he see
empty folder in Dropbox Cloud!
Popular folder encryption software on Windows and Mac OS works more user
friendly - it store encrypted data at same folder, and when user try to open it
- ask password and mount unencryted data at same location, so this work
transparently for users and much more user friendly. So users can encrypt any
folder via simple clicks and be sure, that encrypted data storage will not
moved to another location, but stay here in this folder.
Can Plasma Vault implement same way of mounting - mount unencrypted folder at
same location, that encrypted data is stored, but not in separate crypted
folder on another directory?
--
You are receiving this mail because:
You are watching all bug changes.
