From: Alan Cox <gnomes@lxorguk.ukuu.org.uk>
To: Benjamin Drung <benjamin.drung@profitbricks.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Matthew Garrett <matthew.garrett@nebula.com>,
Jeremy Kerr <jk@ozlabs.org>,
Matt Fleming <matt@codeblueprint.co.uk>,
linux-efi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Read-protected UEFI variables
Date: Mon, 19 Feb 2018 20:24:40 +0000 [thread overview]
Message-ID: <20180219202440.2e80dfbc@alans-desktop> (raw)
In-Reply-To: <1518614486.4749.33.camel@profitbricks.com>
> If the UEFI is as secure as storing an unencrypted file on a hard
> drive, I am satisfied. Or do you have a better idea where to store the
> SSH keys for a diskless system that boots via network?
Store them in the TPM ?
If you are booting over a network and not doing some kind of TPM based
trusted boot check you already lost to a network attacker
Alan
prev parent reply other threads:[~2018-02-19 20:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 12:52 Read-protected UEFI variables Benjamin Drung
2018-02-14 13:09 ` Ard Biesheuvel
2018-02-14 13:21 ` Benjamin Drung
2018-02-14 13:21 ` Benjamin Drung
[not found] ` <1518614486.4749.33.camel-EIkl63zCoXaH+58JC4qpiA@public.gmane.org>
2018-02-14 18:18 ` Môshe van der Sterre
2018-02-14 18:18 ` Môshe van der Sterre
2018-02-14 19:05 ` Benjamin Drung
2018-02-14 20:33 ` Austin S. Hemmelgarn
2018-02-15 19:04 ` Ard Biesheuvel
2018-02-19 20:24 ` Alan Cox [this message]
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=20180219202440.2e80dfbc@alans-desktop \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=ard.biesheuvel@linaro.org \
--cc=benjamin.drung@profitbricks.com \
--cc=jk@ozlabs.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=matthew.garrett@nebula.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.