From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Cryptfs
Date: Sun, 30 Mar 2008 14:06:44 +0100 [thread overview]
Message-ID: <20080330140644.63d0bf61@loonquawl.digimed.co.uk> (raw)
In-Reply-To: <200803300950.53721.dirk.heinrichs@online.de>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
On Sun, 30 Mar 2008 09:50:47 +0200, Dirk Heinrichs wrote:
> > However, the setup doesn't work. I'm not asked for the passphrase, the
> > mappings are not created. What did I forget?
>
> That the mappings are created all in one go before anything is mounted,
> so you can't put the keyfile for /var into /boot. The only thing that
> would work is to put the keyfile on the root fs, because that's the
> only one that is mounted when the mappings are created, like:
You can if you add
pre_mount="mount /dev/mapper/boot /boot"
to the boot stanza of dmcrypt, it forces the filesystem to be mounted
immediately.
I ue a variant of this, where keys are stored on a dedicated partition.
The pre_mount and post_mount (which unmounts the filesystem) ensure that
the keys are only visible for as long as it takes to mount the other
filesystems.
--
Neil Bothwick
Thesaurus: ancient reptile with an excellent vocabulary
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-03-30 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-29 17:32 [gentoo-user] Cryptfs Florian Philipp
2008-03-30 7:50 ` Dirk Heinrichs
2008-03-30 11:24 ` Florian Philipp
2008-03-30 11:24 ` Dirk Heinrichs
2008-03-30 13:06 ` Neil Bothwick [this message]
2008-03-30 16:50 ` Dirk Heinrichs
2008-03-30 20:13 ` Neil Bothwick
2008-03-31 6:36 ` Dirk Heinrichs
2008-03-31 8:11 ` Neil Bothwick
2008-03-31 16:15 ` Dirk Heinrichs
2008-03-31 22:11 ` Neil Bothwick
2008-04-01 6:04 ` Dirk Heinrichs
2008-04-01 7:49 ` Neil Bothwick
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=20080330140644.63d0bf61@loonquawl.digimed.co.uk \
--to=neil@digimed.co.uk \
--cc=gentoo-user@lists.gentoo.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