public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Matthew Garrett: Producing a trustworthy x86-based Linux appliance
Date: Thu, 03 Jun 2021 13:40:29 +0100	[thread overview]
Message-ID: <771B31EE-234B-4176-9C93-AD56F3677501@ipfire.org> (raw)
In-Reply-To: <893e5963-63e8-4012-1a1f-f0979649e18e@ipfire.org>

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

Hello,

I have seen this article as well, but I did not take away much from it.

It says to me:

* You cannot trust hardware
* You cannot trust firmware

And so any software running on top of that cannot validate itself. We just have to hope for the best.

-Michael

> On 2 Jun 2021, at 22:25, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello *,
> 
> in case anybody still needs reading matter, https://mjg59.dreamwidth.org/57199.html might
> be worth a lecture - if you trust the (x86) hardware, that is. :-)
> 
> Thanks, and best regards,
> Peter Müller


  reply	other threads:[~2021-06-03 12:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 21:25 Peter Müller
2021-06-03 12:40 ` Michael Tremer [this message]
2021-06-06  9:25   ` Bernhard Bitsch

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=771B31EE-234B-4176-9C93-AD56F3677501@ipfire.org \
    --to=michael.tremer@ipfire.org \
    --cc=development@lists.ipfire.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