ecryptfs team mailing list archive

[Dustin Kirkland <dustin.kirkland@xxxxxxxxx>]

This is fixed.  You should be able to set any directory owned by the
user in ~/.ecryptfs/Private.mnt.

Traditionally, this file either says:

/home/kirkland

or

/home/kirkland/Private

But it should be anything you want, assuming the directory exists, and
is owned by the user.

:-Dustin

** Changed in: ecryptfs-utils (Ubuntu)
       Status: Confirmed => Fix Released

-- 
suggestion: do not hardcode the ~/Private path in ecryptfs-setup-private
https://bugs.launchpad.net/bugs/405402
You received this bug notification because you are a member of eCryptfs,
which is subscribed to ecryptfs-utils in ubuntu.

Status in “ecryptfs-utils” package in Ubuntu: Fix Released

Bug description:
Binary package hint: ecryptfs-utils

It would be nice if the path ~/Private could be given as an option when ecryptfs-setup-private is run, instead of being hardcoded. This way, file managers such as Dolphin and Nautilus could have options in their context menus to "Encrypt this folder".

Does this only affect ecryptfs-setup-private or are changes necessary to the other tools bundled in the ecryptfs-utils package?