ecryptfs team mailing list archive

[Dustin Kirkland <dustin.kirkland@xxxxxxxxx>]

The ecryptfs-utils-66 version solves this by allowing the user to choose
their mountpoint by setting the path in the file
~/.ecryptfs/Private.mnt.

I'm working on syncing that to Jaunty.

:-Dustin

** Also affects: ecryptfs
   Importance: Undecided
       Status: New

** Changed in: ecryptfs
     Assignee: (unassigned) => Dustin Kirkland (kirkland)
       Status: New => Fix Released

-- 
Cannot specify location of Private directory
https://bugs.launchpad.net/bugs/294888
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in eCryptfs - Enterprise Cryptographic Filesystem: Fix Released
Status in “ecryptfs-utils” source package in Ubuntu: New

Bug description:
Binary package hint: ecryptfs-utils

There doesn't appear to be anyway to set up the Private directory in any location other than ~/Private.  The use case here is that to support suspend/hibernate, I've put my /home on the tiny 4Gb partition on my EEE 701 netboot.  However, I then symlink all my directories in Home (such Pictures, Videos, Music, etc) to a 32Gb SD card which is mounted as /media/MyData.  I'd like to put the encrypted directory on that card and not on /home.

I've tried creating a symlink called Data inside ~/Private to a directory on my card.  However, when I created a text file by editing ~/Private/Data/test.txt, then running /sbin/umount.ecryptfs_private, I was dismayed to discover that the text file was written to my media card unencrypted.  This doesn't appear to be a solution.

I also tried symlinking ~/.Private to a directory on the media card then re-running ecryptfs-setup-private, but sadly it complains that .Private is not empty (although it is, hidden files and all) and fails to complete the process.

My lack of fundamental understanding of ecryptfs is clearly a barrier here, but perhaps someone more knowledgeable than I can find a solution.  This bug is opened in the spirit that this should be an option in the ecryptfs-setup-private process, rather than finding a hack that makes the change after the fact.