From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: tmp on tmpfs
Date: Thu, 25 May 2017 08:23:39 -0400 [thread overview]
Message-ID: <CAGfcS_=DWcO4YZTxkiHkB-Qv0y5+P3j4p3TiD0EKSRNM2gO3AQ@mail.gmail.com> (raw)
In-Reply-To: <20170525130407.64d28784@jupiter.sol.kaishome.de>
On Thu, May 25, 2017 at 7:04 AM, Kai Krakow <hurikhan77@gmail.com> wrote:
> Am Thu, 25 May 2017 08:34:10 +0200
> schrieb "J. Roeleveld" <joost@antarean.org>:
>
>> It is possible. I have it set up like that on my laptop.
>> Apart from a small /boot partition. The whole drive is encrypted.
>> Decryption keys are stored encrypted in the initramfs, which is
>> embedded in the kernel.
>
> And the kernel is on /boot which is unencrypted, so are your encryption
> keys. This is not much better, I guess...
>
Agree. There are only a few ways to do persistent encryption in a secure way:
1. Require entry of a key during boot, protected by lots of rounds to
deter brute force.
2. Store the key on some kind of hardware token that the user keeps
on their person.
3. Store the key in a TPM, protected either by:
a. entry of a PIN/password of some sort with protections on attempt
frequency/total
b. verification of the boot path (which should be possible with
existing software on linux, but I'm not aware of any distro that
actually implements this)
If you don't have hibernation then you can just generate a random key
on boot, and that is very secure, but your swap is unrecoverable after
power-off.
Of the options above 3b is the only one that really lets you do this
with the same level of convenience. This is how most full-drive
encryption solutions work in the Windows world. Chromebooks use a
variation on 3a I believe using your google account password as one
component of the key and putting it through the TPM to have a hardware
component and to throttle attempts.
--
Rich
next prev parent reply other threads:[~2017-05-25 12:23 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-24 5:16 [gentoo-user] tmp on tmpfs Ian Zimmerman
2017-05-24 5:34 ` gentoo-user
2017-05-24 6:00 ` [gentoo-user] " Kai Krakow
2017-05-24 17:05 ` Kai Krakow
2017-05-25 18:46 ` [gentoo-user] Puzzled by zswap [Was: tmp on tmpfs] Ian Zimmerman
2017-05-25 19:16 ` [gentoo-user] " Martin Vaeth
2017-05-26 6:00 ` Kai Krakow
2017-05-24 18:34 ` [gentoo-user] Re: tmp on tmpfs Ian Zimmerman
2017-05-24 19:30 ` Rich Freeman
2017-05-24 21:16 ` Andrew Savchenko
2017-05-24 22:40 ` Rich Freeman
2017-05-25 6:34 ` J. Roeleveld
2017-05-25 11:04 ` Kai Krakow
2017-05-25 12:23 ` Rich Freeman [this message]
2017-05-25 14:16 ` J. Roeleveld
2017-05-25 16:06 ` Rich Freeman
2017-05-25 16:28 ` J. Roeleveld
2017-05-25 16:41 ` Rich Freeman
2017-05-25 3:38 ` Kai Krakow
2017-05-25 7:19 ` J. Roeleveld
2017-05-25 3:36 ` Kai Krakow
2017-05-24 17:00 ` [gentoo-user] " R0b0t1
2017-05-24 6:03 ` Andrew Tselischev
2017-05-24 9:34 ` Rich Freeman
2017-05-24 9:43 ` gentoo-user
2017-05-24 9:54 ` Rich Freeman
2017-05-24 12:45 ` Andrew Savchenko
2017-05-25 4:45 ` [gentoo-user] " Martin Vaeth
2017-05-25 7:24 ` Mick
2017-05-25 15:46 ` Martin Vaeth
2017-05-25 22:36 ` [gentoo-user] " Kent Fredric
2017-05-28 10:07 ` Mick
2017-05-31 0:36 ` Kent Fredric
2017-05-31 7:33 ` Mick
2017-05-24 18:46 ` [gentoo-user] " Nikos Chantziaras
-- strict thread matches above, loose matches on Subject: below --
2017-05-29 11:09 [gentoo-user] Kernel did not finding root partition Raphael MD
2017-05-29 11:19 ` Rasmus Thomsen
2017-05-29 17:48 ` [gentoo-user] " Kai Krakow
2017-05-29 18:07 ` Raphael MD
2017-05-29 18:16 ` Neil Bothwick
2017-05-29 19:42 ` Kai Krakow
2017-05-30 8:26 ` Peter Humphrey
2017-05-30 17:08 ` Raphael MD
2017-05-30 18:05 ` Mick
2017-05-30 19:28 ` Kai Krakow
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='CAGfcS_=DWcO4YZTxkiHkB-Qv0y5+P3j4p3TiD0EKSRNM2gO3AQ@mail.gmail.com' \
--to=rich0@gentoo.org \
--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