[Bug 575096] Re: The default ~/Private name is not very clear

2010-05-05 Thread ceg
I mean "Private" does make good sense for a subdirectory provided to users to keep files private from other users of the system, regardless if it is (on-disk) encrypted or not. -- The default ~/Private name is not very clear https://bugs.launchpad.net/bugs/575096 You received this bug notificatio

[Bug 575096] Re: The default ~/Private name is not very clear

2010-05-05 Thread ceg
I see, thank your the message. Indeed, "Private" makes a nice contrast with "Public", but to keeping something "Private" within a filesystem isn't necessarily much connected with on-disk-encryption at all, or would you think otherwise? I do understand we're not going to change the default crypt-d

Re: [Bug 575096] Re: The default ~/Private name is not very clear

2010-05-05 Thread Dustin Kirkland
When I first proposed the feature at UDS Prague in May 2008, I suggested "Confidential". The Ubuntu core development team instead settled on "Private", as it made for a nice contrast with the "Public" directory. I seriously doubt that this default is going to change. If you would like to discuss

[Bug 575096] Re: The default ~/Private name is not very clear

2010-05-05 Thread ceg
Thanks, that is very good you already implemented the path to be configurable. The issue here is more about the particular default, though. People using the "user private group" scheme (used and advocated for user collaboration in debian/ubuntu system, but still broken due to some minor bugs) use

[Bug 575096] Re: The default ~/Private name is not very clear

2010-05-05 Thread Dustin Kirkland
You can rename that to whatever you want, in ~/.ecryptfs/Private.mnt. ** Changed in: ecryptfs-utils (Ubuntu) Status: New => Won't Fix -- The default ~/Private name is not very clear https://bugs.launchpad.net/bugs/575096 You received this bug notification because you are a member of Ubunt