ecryptfs-utils private directory should support translations of "Private"
Bug #247421 reported by
Dustin Kirkland
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eCryptfs |
Fix Released
|
Undecided
|
Dustin Kirkland | ||
ecryptfs-utils (Ubuntu) |
Fix Released
|
Wishlist
|
Dustin Kirkland |
Bug Description
Binary package hint: ecryptfs-utils
At https:/
Milan71 wrote:
"I'd like to know whether you've thought about a way of translating the name of this directory? It would be good if this 'Private' dir was included in the XDG User Dirs specification, since it is a common use case. But waiting for this, you may need something like a patch for xdg-user-dirs update to achieve this."
Related branches
To post a comment you must log in.
I absolutely want to support translations of the "Private" directory name, and it's definitely on my agenda.
This is a little bit complex at the moment. I have painstakingly created a setuid binary, mount.encrypted _private, that allows non-privileged users to mount their encrypted private directory. In order to pass the multiple levels of audits required to enable such a powerful setuid utility, I had to hardcode a couple of things.
Namely, the algorithm (aes), the key bytes (16), and the directory names ($HOME/.Private and $HOME/Private). My intention is to make each of these 3 parameters configurable by the system administrator in a /etc/ecryptfs.conf (perm 644) file. The key is that we cannot allow the user to arbitrarily choose the name of the directory in order to prevent a multitude of vulnerabilities.
:-Dustin