From: Martin Steigerwald <ms@teamix.de>
To: Dustin Kirkland <dustin.kirkland@gazzang.com>
Cc: ecryptfs@vger.kernel.org
Subject: Re: encryption metadata not stored with filesystem
Date: Tue, 20 Dec 2011 10:53:11 +0100 [thread overview]
Message-ID: <201112201053.12281.ms@teamix.de> (raw)
In-Reply-To: <CANT6BaOtumjj+kJTsDD92YPBKXqnw0Nw8s24B05Wo2agi2oV1A@mail.gmail.com>
Am Montag, 19. Dezember 2011 schrieb Dustin Kirkland:
> On Mon, Dec 19, 2011 at 6:36 AM, Martin Steigerwald <ms@teamix.de> wrote:
> > 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.
>
> Thanks for that suggestion. I've actually just created a bug to track
> this. I'll try to get this working better this week:
> * https://bugs.launchpad.net/ecryptfs/+bug/906550
Thanks, Dustin.
One part of my suggestion was to store the configuration of an ecryptfs
filesystem within the encrypted directory.
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.
When I manage to dig out my Launchpad account or create a new one for my
company's mail address I add that to the bug report.
Ciao,
--
Martin Steigerwald - teamix GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90
next prev parent reply other threads:[~2011-12-20 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-19 12:36 encryption metadata not stored with filesystem Martin Steigerwald
2011-12-19 21:53 ` Dustin Kirkland
2011-12-20 9:53 ` Martin Steigerwald [this message]
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=201112201053.12281.ms@teamix.de \
--to=ms@teamix.de \
--cc=dustin.kirkland@gazzang.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.