ecryptfs team mailing list archive

[Dustin Kirkland <dustin.kirkland@xxxxxxxxx>]

Thanks for the report, Jamie.

I'm actually working on the first part of this (arbitrarily choosing
where to perform the mount) as part of the encrypted $HOME work.

The latter (do-not-automount, do-not-autounmount), is also easy to add,
and a good idea.

The more complicate aspect of your request is the ability to have
multiple Private directories, each being handled independently.  I'll
need to give some thought as to the best way to handle this...

:-Dustin

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

** Changed in: ecryptfs
   Importance: Undecided => Medium
     Assignee: (unassigned) => Dustin Kirkland (kirkland)
       Status: New => Triaged

-- 
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: Triaged
Status in “ecryptfs-utils” source package in Ubuntu: New

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.