[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2871941d922a30334741081640ff5f4105100d00.camel@linux.intel.com>
Date: Mon, 18 May 2020 22:36:42 +0300
From: Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
To: Thomas Gleixner <tglx@...utronix.de>,
Sasha Levin <sashal@...nel.org>
Cc: linux-kernel@...r.kernel.org, bp@...en8.de, luto@...nel.org,
hpa@...or.com, dave.hansen@...el.com, tony.luck@...el.com,
ak@...ux.intel.com, ravi.v.shankar@...el.com,
chang.seok.bae@...el.com
Subject: Re: [PATCH v12 00/18] Enable FSGSBASE instructions
On Mon, 2020-05-18 at 11:51 +0200, Thomas Gleixner wrote:
> Sasha Levin <sashal@...nel.org> writes:
> > On Fri, May 15, 2020 at 12:24:14PM +0300, Jarkko Sakkinen wrote:
> > > Can you put me to the CC-loop for this patches. Some SGX-enabled
> > > frameworks such as Graphene use out-of-tree changes to achieve this.
> > > That's where the interest to possibly test this comes from.
> >
> > Indeed, we've seen a few hacks that basically just enable FSGSBASE:
> >
> > - https://github.com/oscarlab/graphene-sgx-driver
> > - https://github.com/occlum/enable_rdfsbase
>
> I'm really amazed by all these security experts enabling a full root
> hole. It clearly puts the SGX hypocrisy into perspective.
>
> Thanks,
>
> tglx
That's exactly why I'm interested to test this series.
/Jarkko
Powered by blists - more mailing lists