This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GCC and Meltdown and Spectre vulnerabilities

From: Florian Weimer <fw at deneb dot enyo dot de>
To: timofonic timofonic <timofonic at gmail dot com>
Cc: gcc at gcc dot gnu dot org
Date: Fri, 05 Jan 2018 22:35:20 +0100
Subject: Re: GCC and Meltdown and Spectre vulnerabilities
Authentication-results: sourceware.org; auth=none
References: <CAMfHzOtmtS9JcbXz0S4PF+ecpCL7nFa=6nLR56S7AY-jMazyYQ@mail.gmail.com> <99ECE1CD-F283-414C-9495-DB5D41FCFDB6@acm.org> <CAKOQZ8zesWkrAh-e8eLksj15nEKqk-f6SMH1S7ysbEbKXwAV4w@mail.gmail.com> <CAPDh1ToHYm-HPAhZv9akYb4b53zSJPgRP28yxfC_bPN2Ew5J7Q@mail.gmail.com>

* timofonic timofonic:

> Paranoid jails/sandboxes inside a virtual machine may mitigate a lot
> the risk for those untrusted binaries, right?

Someone needs to impelement those sandboxes and virtual machines, and
GCC changes may help with writing them in such a way that they are
less exposed to these vulnerabilities.

(I'm not sure if this is the right way forward—I'm just trying to
explain the rationale for potential GCC changes.)

References:
- GCC and Meltdown and Spectre vulnerabilities
  - From: Eric Gallager
- Re: GCC and Meltdown and Spectre vulnerabilities
  - From: Zan Lynx
- Re: GCC and Meltdown and Spectre vulnerabilities
  - From: Ian Lance Taylor via gcc
- Re: GCC and Meltdown and Spectre vulnerabilities
  - From: timofonic timofonic

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]