public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Philipp <lists@f_philipp.fastmail.net>
To: Gentoo-User <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] Initrd-script questions
Date: Tue, 18 Mar 2008 17:56:30 +0100	[thread overview]
Message-ID: <1205859390.7981.16.camel@NOTE_GENTOO64.PHHEIMNETZ> (raw)

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

Hi list!

I'd like to have some advice on my situation:

I have a custom init-script (derived from genkernel). What it already
does is to let gpg ask for a passphrase to decrypt a file on /boot and
then to use to content of that file as the key to a LUKS-formatted swap
(logical volume) which is then used to resume from disk.

What I would also like to do is to use the very same key for other
lvm-volumes like /var and /var/tmp but that doesn't seem that easy.

First idea: Just do the same as with the swap-volume. However, all other
mappings are gone after resuming/booting.

Second idea: Write the plaintext-keyfile to /boot and then use it
via /etc/conf.d/cryptfs before removing it in a secure manner (srm,
provided by app-misc/secure-delete). Problem: When resuming, /boot is
already mounted. Writing to it and then resuming leads to filesystem
corruption.

Third idea: Using a dedicated volume for storing the plaintext key.
Cumbersome, doesn't reduce the risk that srm isn't enough to protect the
key.

So ... what I'd need is a way to transfer data between an initial
ramdisk and the real init. Ideally in form of tmpfs-mountpoint.

I don't think my odds are very high but I just wanted to ask...

Thanks in advance!

Florian Philipp

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2008-03-18 16:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-18 16:56 Florian Philipp [this message]
2008-03-18 17:27 ` [gentoo-user] Initrd-script questions 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=1205859390.7981.16.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