ecryptfs-setup-private should create an .ecryptfsrc file
Bug #906550 reported by
Dustin Kirkland
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
eCryptfs |
Triaged
|
Wishlist
|
Dustin Kirkland |
Bug Description
ecryptfs-
> merkaba:~> cat .ecryptfsrc
> ecryptfs_
> ecryptfs_sig=[…]
> ecryptfs_
> ecryptfs_xattr
> ecryptfs_
> ecryptfs_cipher=aes
> ecryptfs_
Changed in ecryptfs: | |
status: | New → Triaged |
importance: | Undecided → High |
assignee: | nobody → Dustin Kirkland (kirkland) |
To post a comment you must log in.
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://