From: Florian Philipp <lists@f_philipp.fastmail.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Cryptfs
Date: Sun, 30 Mar 2008 13:24:34 +0200 [thread overview]
Message-ID: <1206876274.13252.19.camel@NOTE_GENTOO64.PHHEIMNETZ> (raw)
In-Reply-To: <200803300950.53721.dirk.heinrichs@online.de>
[-- Attachment #1: Type: text/plain, Size: 1966 bytes --]
On Sun, 2008-03-30 at 09:50 +0200, Dirk Heinrichs wrote:
> Am Samstag, 29. März 2008 schrieb Florian Philipp:
>
> > My goal is to open a Luks-mapping for /var with a gpg-encrypted file
> > on /boot and then open a mapping for /var/tmp with a plaintext file
> > on /var.
>
> See below. But while we're at it, can anybody tell me what's the advantage of
> a gpg-encrypted keyfile over a keyfile generated from /dev/urandom?
Keys for urandom work great for /tmp and swap but how should I use this
for a partition which is supposed to keep its content between reboots?
>
> > I thought it would work with the following settings:
> >
> > /etc/conf.d/cryptfs
>
> It's /etc/conf.d/dmcrypt nowadays.
Interesting, why is there no hint that cryptfs is deprecated/obsolete?
>
> > target=var
> > source='/dev/mapper/vg-crypt_var'
> > key='/boot/key.gpg:gpg'
> >
> > target=var_tmp
> > source='/dev/mapper/vg-crypt_var_tmp'
> > key='/var/lib/tmp_key'
> >
> >
> > I've read the warning in /etc/conf.d/cryptfs about /usr on a separate
> > partition and followed their advice.
>
> Which warning, btw.? Works just fine here.
>
"# Note when using gpg keys and /usr on a separate partition, you will
# have to copy /usr/bin/gpg to /bin/gpg so that it will work properly
# and ensure that gpg has been compiled statically.
# See http://bugs.gentoo.org/90482 for more information."
> > 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:
>
> target='c-usr'
> source='/dev/evms/usr'
> key='/etc/crypt/keyfile'
>
> Bye...
>
> Dirk
Thanks, I'll try it.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-30 10:24 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 [this message]
2008-03-30 11:24 ` Dirk Heinrichs
2008-03-30 13:06 ` Neil Bothwick
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=1206876274.13252.19.camel@NOTE_GENTOO64.PHHEIMNETZ \
--to=lists@f_philipp.fastmail.net \
--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