← Back to team overview

ecryptfs team mailing list archive

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

 

Dustin,

That's actually how I'm doing currently (with Documents/ and couple of
other folders symlinked), and it works just fine. What I was looking
for, however, was the ability to easily create new encrypted folders
from dolphin's/nautilus' context menus; a simple right click and
"encrypt this folder". Or, rather, the underlying mechanism to enable me
to easily write such scripts.

Time to file a new wishlist item? ;-)

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