ecryptfs team mailing list archive

[Dustin Kirkland <dustin.kirkland@xxxxxxxxx>]

Fix committed upstream.  This will be in ecryptfs-utils-72 when
released.

:-Dustin

** Changed in: ecryptfs
       Status: Triaged => Fix Committed

** Changed in: ecryptfs-utils (Ubuntu)
       Status: Triaged => Fix Committed

-- 
provide more options to ecryptfs-setup-private
https://bugs.launchpad.net/bugs/301759
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 Committed
Status in “ecryptfs-utils” source package in Ubuntu: Fix Committed

Bug description:
Binary package hint: ecryptfs-utils

It would be nice if ecyptfs-setup-private could be used to setup ecryptfs partitions in a generic way. Eg:

$ ecryptfs-setup-private -d $HOME/foo -n

Where '-d $HOME/foo' tells ecryptfs-setup-private to use $HOME/foo instead of ~/Private and '-n' tells ecryptfs to not perform auto-mounting. The idea behind this is to support:

1. ~/Private (like now)
2. ~/foo (auto-mounted)
3. ~/bar (not auto-mounted)
4. any combination of the above

This is useful for when you may want an auto-mounted ~/Private for frequently accessed data, but a separate non-auto-mounted area for things that are only infrequently accessed.