lkml.org 
[lkml]   [2018]   [Jun]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [intel-sgx-kernel-dev] [PATCH v11 13/13] intel_sgx: in-kernel launch enclave
    From
    Date
    On Thu, 2018-06-21 at 08:32 -0400, Nathaniel McCallum wrote:
    > This implies that it should be possible to create MSR activation (and
    > an embedded launch enclave?) entirely as a UEFI module. The kernel
    > would still get to manage who has access to /dev/sgx and other
    > important non-cryptographic policy details. Users would still be able
    > to control the cryptographic policy details (via BIOS Secure Boot
    > configuration that exists today). Distributions could still control
    > cryptographic policy details via signing of the UEFI module with their
    > own Secure Boot key (or using something like shim). The UEFI module
    > (and possibly the external launch enclave) could be distributed via
    > linux-firmware.
    >
    > Andy/Neil, does this work for you?

    Nothing against having UEFI module for MSR activation step.

    And we would move the existing in-kernel LE to firmware so that it is
    avaible for locked-in-to-non-Intel-values case?

    /Jarkko

    \
     
     \ /
      Last update: 2018-06-25 11:42    [W:3.414 / U:1.416 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site