Uploaded a fix to karmic, though it doesn't involve a bind mount.
Instead, all of /var/lib/ecryptfs and the user's .Private dir has been
moved to /home/.ecryptfs/$USER.
This allows the user to access this data, and back it up whether or not
the home dir is mounted.
I actually think it might be a good idea to provide something like this
for Jaunty users.
I suspect a number of Jaunty users upgrading to Karmic may well
inadvertently delete their /var/lib/ecryptfs data, and not have a
backup.
:-Dustin
** Also affects: ecryptfs-utils (Ubuntu Jaunty)
Importance: Undecided
Status: New
** Changed in: ecryptfs-utils (Ubuntu Jaunty)
Importance: Undecided => Wishlist
** Changed in: ecryptfs-utils (Ubuntu Jaunty)
Status: New => Confirmed
** Changed in: ecryptfs-utils (Ubuntu Jaunty)
Importance: Wishlist => Low
** Changed in: ecryptfs-utils (Ubuntu Jaunty)
Milestone: None => jaunty-updates
** Changed in: ecryptfs-utils (Ubuntu Jaunty)
Assignee: (unassigned) => Dustin Kirkland (kirkland)
** Summary changed:
- establish ro,bind mount of /home for backup purposes
+ provide access to .ecryptfs and .Private for backup purposes
** Changed in: ecryptfs-utils (Ubuntu Jaunty)
Importance: Low => High
--
provide access to .ecryptfs and .Private for backup purposes
https://bugs.launchpad.net/bugs/371719
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
