EcryptFS development
 help / color / mirror / Atom feed
From: Martin Steigerwald <ms@teamix.de>
To: ecryptfs@vger.kernel.org
Subject: encryption metadata not stored with filesystem
Date: Mon, 19 Dec 2011 13:36:04 +0100	[thread overview]
Message-ID: <201112191336.05938.ms@teamix.de> (raw)

Hi!

On trying to work with ecryptfs I have found that I have to store ecryptfs 
configuration in an undocumented file ~/.ecryptfsrc like:

merkaba:~> cat .ecryptfsrc 
ecryptfs_unlink_sigs
ecryptfs_sig=[…]
ecryptfs_fnek_sig=[…]
ecryptfs_xattr
ecryptfs_key_bytes=32
ecryptfs_cipher=aes
ecryptfs_passthrough=n

in order to mount ecryptfs without mount options.

This makes handling of ecryptfs filesystem more complicated than encfs, since 
encfs seems to store encryption metadata in the encrypted directory itself:

merkaba:~> ls -l /home/.ms2/.encfs5
-rw-r----- 1 root root 241 Mai 19  2008 /home/.ms2/.encfs5

Thus with ecryptfs I have to save the encrypted directory and the filesystem 
settings for a backup while with encfs its enough to copy the encrypted 
directory.

Please consider to add this feature in ecryptfs.

It will also make setting up ecryptfs easier.

Thanks,
-- 
Martin Steigerwald - teamix GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90

             reply	other threads:[~2011-12-19 12:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-19 12:36 Martin Steigerwald [this message]
2011-12-19 21:53 ` encryption metadata not stored with filesystem Dustin Kirkland
2011-12-20  9:53   ` Martin Steigerwald
2011-12-22  2:49     ` Dustin Kirkland

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201112191336.05938.ms@teamix.de \
    --to=ms@teamix.de \
    --cc=ecryptfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox