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

2009-09-24 Thread Khashayar Naderehvandi
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 fo

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

2009-09-19 Thread Dustin Kirkland
Right, it only supports a single line in that file. You get one place to put your private data. You can move as much data inside of that directory as you want, creating as many subfolders. Furthermore, you can use symlinks else where. In your case, I'd recommend moving your Documents directory

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

2009-09-19 Thread Khashayar Naderehvandi
That's great news, thanks! One question though: Is it supposed to work with multiple lines in Private.mnt? I tried adding /home/khashayar/Private /home/khashayar/Documents to Private.mnt, but only ~/Private gets mounted. -- suggestion: do not hardcode the ~/Private path in ecryptfs-setup-priva

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

2009-09-18 Thread Dustin Kirkland
This is fixed. You should be able to set any directory owned by the user in ~/.ecryptfs/Private.mnt. Traditionally, this file either says: /home/kirkland or /home/kirkland/Private But it should be anything you want, assuming the directory exists, and is owned by the user. :-Dustin ** Change

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

2009-07-27 Thread Khashayar Naderehvandi
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 i

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

2009-07-27 Thread Dustin Kirkland
Good idea. Will do. Attaching a well-formed, tested patch would be welcome :-) *hint, hint* :-Dustin ** Changed in: ecryptfs-utils (Ubuntu) Status: New => Confirmed ** Changed in: ecryptfs-utils (Ubuntu) Importance: Undecided => Wishlist -- suggestion: do not hardcode the ~/Privat