2017-11-21 23:46:30

by Jethro Beekman

[permalink] [raw]
Subject: Re: [PATCH v5 11/11] intel_sgx: driver documentation

On 2017-11-21 04:47, Borislav Petkov wrote:
> On Tue, Nov 21, 2017 at 02:38:54PM +0200, Jarkko Sakkinen wrote:
>> Try to start LE. If it doesn't start i.e. is signed with a different
>> root key than the one inside MSRs, then fail the initialization.
>
> But what if the one inside the MSRs is from the fw vendor and I don't
> trust it?
>

Boris & Peter: this key has nothing to do with "trust" or "security". As
Sean mentioned in the other thread (PATCH v5 06/11) the kernel is fully
capable of enforcing any security policy on its own without help of an
enclave.

> I.e., let the owner really own the hardware she paid money for.

Yes, let's. Processors with SGX have been commercially available for
over 2 years (and I have owned them for the same time). Why is it that I
still can't use a mainline kernel to get access to all the cabapilities
of my 2-year old hardware? Let's try not to put too much policy in the
kernel and let userspace decide.

Jethro Beekman

From 1584680058736199509@xxx Tue Nov 21 12:51:11 +0000 2017
X-GM-THRID: 1583981482468800352
X-Gmail-Labels: Inbox,Category Forums,HistoricalUnread