all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Leah Rowe <info@gluglug.org.uk>
Cc: guix-devel@gnu.org
Subject: Re: What do Meltdown and Spectre mean for libreboot x200 user?
Date: Mon, 15 Jan 2018 14:25:41 +0100	[thread overview]
Message-ID: <87lggzb6ei.fsf@igalia.com> (raw)
In-Reply-To: <6e931622-65fc-fe0b-491f-3e94c6acdf0b@gluglug.org.uk> (Leah Rowe's message of "Mon, 15 Jan 2018 11:32:40 +0000")

Greets,

On Mon 15 Jan 2018 12:32, Leah Rowe <info@gluglug.org.uk> writes:

> The implications [of Meltdown/Spectre] at firmware level are
> non-existent (for instance, these attacks can't, to my knowledge, be
> used to actually run/modify malicious code, just read memory, so it's
> not as if some evil site could install malicious boot firmware in your
> system).

I agree that it's unlikely that a site could install boot firmware, but
AFAIU it's not out of the realm of possibility.  The vector I see would
be using Meltdown/Spectre to read authentication/capability tokens which
could be used to gain access, either via some other RCE vuln or possibly
via remote access.  Maybe evil code could find an SSH private key in a
mapped page, for example, which the evil server could use to SSH
directly to your machine.  But I admit that it's a bit farfetched :)

Andy

  reply	other threads:[~2018-01-15 13:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10  8:56 What do Meltdown and Spectre mean for libreboot x200 user? Leah Rowe
2018-01-14 15:17 ` Alex Vong
2018-01-15 11:32   ` Leah Rowe
2018-01-15 13:25     ` Andy Wingo [this message]
2018-01-19 14:26       ` Leah Rowe
2018-01-19 14:29         ` Leah Rowe
  -- strict thread matches above, loose matches on Subject: below --
2018-01-06 13:20 Alex Vong
2018-01-06 17:23 ` Mark H Weaver

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=87lggzb6ei.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=guix-devel@gnu.org \
    --cc=info@gluglug.org.uk \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

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.