One part of my suggestion was to store the configuration of an ecryptfs
filesystem within the encrypted directory[1].
With encfs I can rsync the crypted directory to somewhere else and then just
mount it on the remote machine like I would on my local one. I do not have to
think about copying the ecryptfs configuration as well.
Encfs stores its configuration directly in the encrypted directory like this:
merkaba:~> ls -l /home/.ms2/.encfs5
-rw-r----- 1 root root 241 Mai 19 2008 /home/.ms2/.encfs5
Thanks, Dustin.
One part of my suggestion was to store the configuration of an ecryptfs
filesystem within the encrypted directory[1].
With encfs I can rsync the crypted directory to somewhere else and then just
mount it on the remote machine like I would on my local one. I do not have to
think about copying the ecryptfs configuration as well.
Encfs stores its configuration directly in the encrypted directory like this:
merkaba:~> ls -l /home/.ms2/.encfs5
-rw-r----- 1 root root 241 Mai 19 2008 /home/.ms2/.encfs5
[1] encryption metadata not stored with filesystem on ecryptfs vger kernel org: www.spinics. net/lists/ ecryptfs/ msg00062. html
http://