Date: Fri, 29 Jul 2005 13:52:40 +0200 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: freebsd-security <freebsd-security@freebsd.org>, "Ronnel P. Maglasang" <rmaglasang@infoweapons.com>, Pawel Jakub Dawidek <pjd@freebsd.org>, freebsd-hackers <freebsd-hackers@freebsd.org>, freebsd-geom <freebsd-geom@freebsd.org> Subject: Re: booting gbde-encrypted filesystem Message-ID: <94252.1122637960@phk.freebsd.dk> In-Reply-To: Your message of "Fri, 29 Jul 2005 13:45:48 %2B0200." <20050729134548.1cc28dr8gg0k4k0g@netchild.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <20050729134548.1cc28dr8gg0k4k0g@netchild.homeip.net>, Alexander Leidinger writes: >Pawel Jakub Dawidek <pjd@freebsd.org> wrote: > >> This is not not possible with current GBDE. >> I've patches which allows this here: >> >> http://people.freebsd.org/~pjd/patches/gbde.patch > >I fail to see how this allows an encryted root-FS, it doesn't add gbde >support to boot0(ext) or to the loader. It needs access to an unencrypted >kernel. I don't think this is what Ronnel had in mind (overlooking the fact >that his suggestion to save the passphrase in the loader is insecure). There is a difference between loading the kernel from an encrypted volume (very hard!) and mounting the root filesystem from an encrypted volume (possible with pawels patch. Now of course, if your kernel has been trojaned, you're in trouble, but then again, most people just worry about their data if the machine gets stolen. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?94252.1122637960>