Bug 396334

Summary:	Unencrypt data to same folder that vault encrypted data is located
Product:	[Unmaintained] Plasma Vault	Reporter:	Murz <MurzNN>
Component:	general	Assignee:	Ivan Čukić <ivan.cukic>
Status:	RESOLVED INTENTIONAL
Severity:	wishlist	CC:	nate
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Murz 2018-07-09 08:11:53 UTC

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?

Comment 1 Ivan Čukić 2018-07-13 18:46:30 UTC

I'm sad to mark this as wontfix as the idea is quite nice.

Neither encfs nor cryfs allow what you're asking for. This means that I'd need to find a hackish way to make it look like what you propose is happening without it actually happening which I don't want to do - having hacks like that in security software is a bad idea.

Vault is always security first, usability second.