Bug 400361 - Creating new vault gives error message. Vault subsequently unencrypted.
Summary: Creating new vault gives error message. Vault subsequently unencrypted.
Status: RESOLVED FIXED
Alias: None
Product: Plasma Vault
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Ivan Čukić
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-10-27 11:32 UTC by Paul Worrall
Modified: 2019-04-07 16:11 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Paul Worrall 2018-10-27 11:32:36 UTC
SUMMARY
Using the widget to create a new vault gives error "Unable to perform the operation (error code 1)." and then subsequently opening the vault opens the mount point unencrypted.

STEPS TO REPRODUCE
1. +Create a New Vault...
2. Vault name: MyVault
3. Backend: CryFS (i.e. leave at default setting)
4. Enter and verify password
5. Encrypted data location: /home/paul/.local/share/plasma-vault/MyVault.enc (i.e. the default)
6. Mount point: /home/paul/Vaults/MyVault (i.e. the default)
7. Use the default cipher
8. NOT Limit to selected activities
9. NOT Go offline
10. Click "Create"

OBSERVED RESULT
"Unable to perform the operation (error code 1)."
Dialog stays open
No entry for MyVault in the widget's list of vaults

EXPECTED RESULT
No error msg
Vault is created
Vault appears in widget list

SOFTWARE VERSIONS
Kubuntu 18.10
KDE Plasma Version: 5.14.2 installed via backports PPA
KDE Frameworks Version: 5.51.0
Qt Version: 5.11.1

ADDITIONAL INFORMATION
/home is NFS4 mounted from a server on my private network. (would this make a difference?)

Using the widget as above: 

A new folder "/home/Vaults/MyVault" is created

A new folder "/home/.local/share/plasma-vault/MyVault.enc" is created

/home/.config/plasmavaultrc is updated with:

[/home/paul/.local/share/plasma-vault/MyVault.enc]
activities=
backend=cryfs
lastError=Unknown device (code: 1)
lastStatus=0
mountPoint=/home/paul/Vaults/MyVault
name=MyVault
offlineOnly=false

Next time I log in, MyVault appears in Widget list as a normal folder but the 'mount' button does nothing.

If I choose "Open with File Manager", and enter my password the Vault appears to be opened in Dolphin, but it's actually the unencrypted mount point. (no cryfs filesystem is reported by the 'mount' command).

If I use the widget to delete MyVault and then on the command-line:

cryfs /home/paul/.local/share/plasma-vault/MyVault.enc /home/paul/Vaults/MyVault

and choosing default settings give no error message and basedir is mounted successfully.
Comment 1 Paul Worrall 2018-10-27 11:42:05 UTC
Having created the cryfs system on the command line as described, and edited plasmavaultrc (while logged out of plasma) then the widget mounts and opens the encrypted folder properly
Comment 2 Ivan Čukić 2018-10-28 22:15:41 UTC
What version of cryfs do you have?
Comment 3 Paul Worrall 2018-10-28 22:18:38 UTC
CryFS Version 0.9.9
Comment 4 Ivan Čukić 2019-03-23 10:23:19 UTC
Unfortunately, I haven't been able to reproduce this. Maybe it is NFS's fault, but I don't see a reason for it.
Comment 5 Paul Worrall 2019-04-07 16:11:30 UTC
Thanks for looking into this.  I've rebuilt the NFS server host, upgrading from NFS 4.1 to 4.2 in the process, and now I can no longer reproduce this problem.