ecryptfs team mailing list archive

[Khashayar Naderehvandi <khashayar.lists@xxxxxxxxx>]

Public bug reported:

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?

** Affects: ecryptfs-utils (Ubuntu)
     Importance: Undecided
         Status: New

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

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?