From: Dirk Heinrichs <dirk.heinrichs.ext@nsn.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Cryptfs
Date: Tue, 1 Apr 2008 08:04:10 +0200 [thread overview]
Message-ID: <200804010804.10144.dirk.heinrichs.ext@nsn.com> (raw)
In-Reply-To: <20080331231156.036f2049@loonquawl.digimed.co.uk>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
Am Dienstag, 1. April 2008 schrieb ext Neil Bothwick:
> On Mon, 31 Mar 2008 18:15:54 +0200, Dirk Heinrichs wrote:
> > > That's right, because the keys aren't in /boot ;-)
> >
> > But they are somewhere. He who has cracked your box can simply look
> > into /etc/conf.d/dmcrypt to find out where your keyfile is stored and
> > mount that fs if needed.
>
> Not without the password. That filesystem uses a password, not a keyfile.
You didn't tell this before. Now I finally got the whole picture.
Bye...
Dirk
--
Dirk Heinrichs | Tel: +49 (0)162 234 3408
Configuration Manager | Fax: +49 (0)211 47068 111
Capgemini Deutschland | Mail: dirk.heinrichs@capgemini.com
Wanheimerstraße 68 | Web: http://www.capgemini.com
D-40468 Düsseldorf | ICQ#: 110037733
GPG Public Key C2E467BB | Keyserver: www.keyserver.net
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-04-01 6:04 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
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 [this message]
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=200804010804.10144.dirk.heinrichs.ext@nsn.com \
--to=dirk.heinrichs.ext@nsn.com \
--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