| 1 |
On Sun, 16 Dec 2007 16:34:42 -0800, felix@×××××××.com wrote: |
| 2 |
|
| 3 |
> > Alternatively, you could do the same with the in-kernel ecryptfs. |
| 4 |
> > These two solutions work in much the same way, allowing you to mount |
| 5 |
> > individual directories with their own passwords, so you could have a |
| 6 |
> > single /home with each user's directory having its own password. You |
| 7 |
> > back up the encrypted data, so no passwords are needed for this. |
| 8 |
> |
| 9 |
> ecryptfs-utils apaprently is for ~x86 only. Any idea of when it will |
| 10 |
> be ready for ~amd64? |
| 11 |
|
| 12 |
It worked on amd64 when I tried it. You just need to add the utils package |
| 13 |
to /etc/portage/package.keywords. |
| 14 |
|
| 15 |
> I do have encfs emrrged on all machines, so I can start there with |
| 16 |
> experimentation; it does encrypt file names, but I'd rather have a |
| 17 |
> solid encrypted block than bits and pieces. I suppose that might not |
| 18 |
> matter a whole lot. |
| 19 |
|
| 20 |
ISTR that ecryptfs doesn't encrypt filenames, but it's been a while since |
| 21 |
I used it. In that respect it was inferior to encfs (unless this has |
| 22 |
changed) but it was faster. |
| 23 |
|
| 24 |
|
| 25 |
-- |
| 26 |
Neil Bothwick |
| 27 |
|
| 28 |
"But, I DO know everything." - Q. |
Archives