← Back to team overview

ecryptfs team mailing list archive

Re: [Bug 405402] Re: suggestion: do not hardcode the ~/Private path in ecryptfs-setup-private

 

Right, it only supports a single line in that file.  You get one place
to put your private data.  You can move as much data inside of that
directory as you want, creating as many subfolders.  Furthermore, you
can use symlinks else where.

In your case, I'd recommend moving your Documents directory into
Private, and then symlink it to the location where you want it.

:-Dustin

-- 
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?



References