eCryptfs

ecryptfs-recover-private ignores directory argument and mounts home directory instead

Bug #1313151 reported by Karl-Philipp Richter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
eCryptfs
Incomplete
Undecided
Unassigned

Bug Description

reproduction:
1.) take a /home directory of an other Ubuntu system (in my case it was a backup of another machine, but you might produce one in a VM or do something similar) and put it somewhere outside /home, e.g. /mnt/bla
2.) invoke <code>sudo ecryptfs-recover-private --rw /mnt/bla/.Private</code>
3.) cd /to/the/temporary/mount_point and do some unimportant change (attention: they occur on your $HOME directory (or /home/$USER directory)!!)
4.) changes occur in $HOME or /home/$USER instead of /mnt/bla, i.e. the directory passed as argument

Version ?? (https://bugs.launchpad.net/ecryptfs/+bug/1313152) on Ubuntu 14.04

See original description
Karl-Philipp Richter (krichter722)
description: updated
Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

This is still an issue in 15.04. `ecryptfs-recover-private` does not work (see the other 5! bugs I filed about this package)! In case you're planning to drop support for encryption, please add a warning dialog to the installation routine because users expect encryption to work after checking "encrypt my home directory" and not be in a very unstable state (for > 1 year now), irrecoverable, etc.

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

This seems to happen when mounting `/path/to/oldhome/username/.Private`. The workaround (until the program provides usable feedback, explanations and corner case coverage) is to mount `/mnt/oldhome/.ecryptfs/username/.Private`<ref>http://askubuntu.com/questions/36573/trying-to-mount-old-encrypted-home</ref>.

Jason Xing (wlxing)
Changed in ecryptfs:
status: New → Invalid
Revision history for this message
Tyler Hicks (tyhicks) wrote :

@Jason why did you mark this bug invalid?

Changed in ecryptfs:
status: Invalid → New
Revision history for this message
Jason Xing (wlxing) wrote :

Oh, right. I'm sorry that the comment I made is not posted successfully.

In terms of the "bug description", there are some common parts in these bugs reported before (see bug 1028532, bug 1439825 and bug 1001933). We do not have such a problem and there are no other users affected by this issue. Attached is my test for ecryptfs-recover-private. But marking this as "invalid" is inappropriate, I think. So I'm going to ask @Karl-Philipp Richter. Do you have any information related to this bug in your log? Can you post what information on your console after you enter "sudo ecryptfs-recover-private --rw /mnt/bla/.Private " ?

Revision history for this message
Karl-Philipp Richter (krichter722) wrote :

Over the last 3 years which past until I opened this bug I stopped using ecryptfs because of massive memory and storage leaks - which I didn't report (or maybe did?) because there was no feedback on this issue... - which required to reinstall Ubuntu everytime the issues occured, so I can't test this anymore.

If you don't mind, leave the status Incomplete - I might find the courage to install ecryptfs one day and then deal with/report the numerous issues I encountered, but bug reporting (generally) makes no sense if the issues get only looked at after 3 years.

Revision history for this message
Jason Xing (wlxing) wrote :

I'm sorry for the problem you have. eCryptfs does have some flaws, but not that bad "massive memory and storage leaks". I'm leaving this as incomplete as you said. Any suggestions and comments are welcome:)

Changed in ecryptfs:
status: New → Incomplete
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.