lkml.org 
[lkml]   [2018]   [Jun]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [intel-sgx-kernel-dev] [PATCH v11 13/13] intel_sgx: in-kernel launch enclave
    On Fri, Jun 08, 2018 at 11:50:14AM -0700, Andy Lutomirski wrote:
    > On Fri, Jun 8, 2018 at 10:32 AM Jarkko Sakkinen
    > <jarkko.sakkinen@linux.intel.com> wrote:
    > >
    > > The Launch Enclave (LE) generates cryptographic launch tokens for user
    > > enclaves. A launch token is used by EINIT to check whether the enclave
    > > is authorized to launch or not. By having its own launch enclave, Linux
    > > has full control of the enclave launch process.
    > >
    > > LE is wrapped into a user space proxy program that reads enclave
    > > signatures outputs launch tokens. The kernel-side glue code is
    > > implemented by using the user space helper framework. The IPC between
    > > the LE proxy program and kernel is handled with an anonymous inode.
    > >
    > > The commit also adds enclave signing tool that is used by kbuild to
    > > measure and sign the launch enclave. CONFIG_INTEL_SGX_SIGNING_KEY points
    > > to a PEM-file for the 3072-bit RSA key that is used as the LE public key
    > > pair. The default location is:
    >
    > It might be nice to use the infrastructure that Alexei added for
    > bpfilter (the umh_blob stuff) here, which is slated for merging in
    > this merge window.
    >
    > --Andy

    Thanks, not familiar with this work. Is there any documentation for
    it available?

    /Jarkko

    \
     
     \ /
      Last update: 2018-06-19 17:06    [W:6.790 / U:0.032 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site