ecryptfs team mailing list archive
-
ecryptfs team
-
Mailing list archive
-
Message #01223
[Bug 405402] Re: suggestion: do not hardcode the ~/Private path in ecryptfs-setup-private
Ah, that was good fun while it lasted :)
Although, I'm no programmer by any means, I gave this a shot, figuring
it would be all bash scripts. After a while I realized there's some
hacking needed in mount.ecryptfs_private.c. I tried to poke around with
that, but like I said, I'm no programmer, so it was a fail.
Well, well... I hope someone else is interested enough in having easily
encrypted folders through context menu entries.
--
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: Confirmed
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