[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87o8qly3jo.fsf@nanos.tec.linutronix.de>
Date: Mon, 18 May 2020 11:51:07 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Sasha Levin <sashal@...nel.org>,
Jarkko Sakkinen <jarkko.sakkinen@...ux.intel.com>
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
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
Powered by blists - more mailing lists