Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Subject: Re: [PATCH v5 11/11] intel_sgx: driver documentation
To:     Borislav Petkov <bp@alien8.de>,
        Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
Cc:     Peter Zijlstra <peterz@infradead.org>,
        platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org,
        Thomas Gleixner <tglx@linutronix.de>
References: <20171113194528.28557-1-jarkko.sakkinen@linux.intel.com>
 <20171113194528.28557-12-jarkko.sakkinen@linux.intel.com>
 <20171114083647.uxlaov56s2xw3pua@pd.tnic>
 <20171114204948.f6g2m62kx5gr5xtw@linux.intel.com>
 <20171115115412.uqdy3y74w4sdnzlo@hirez.programming.kicks-ass.net>
 <20171120224623.hpx7zcorrwo4ivhh@linux.intel.com>
 <20171121123854.rv3uxl7zndh3kr2z@linux.intel.com>
 <20171121124739.vszgiz37bhzjfnug@pd.tnic>
From:   Jethro Beekman <jethro@fortanix.com>
Message-ID: <32c3936f-f5f0-cd26-f6f8-6d710b4eb3d6@fortanix.com>
Date:   Tue, 21 Nov 2017 15:45:31 -0800
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101
 Thunderbird/52.4.0
MIME-Version: 1.0
In-Reply-To: <20171121124739.vszgiz37bhzjfnug@pd.tnic>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Received-SPF: None (protection.outlook.com: fortanix.com does not designate
 permitted sender hosts)
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Nov 2017 23:45:35.1040 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 70355a09-0909-4d69-bff4-08d53139f66b
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: de7becae-4883-43e8-82c7-7dbdbb988ae6
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM3PR11MB0921
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

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