{"push_id":2607885135,"size":6,"distinct_size":6,"ref":"refs/heads/master","head":"b15b50638d45d133c84a1b8082ba50df433e2c38","before":"21b2e2d84bd47d7952875669ef1c31fab02e56cb","commits":[{"sha":"38495105c3a518a37dd527f2756388f90557ede0","author":{"name":"Jarkko Sakkinen","email":"6e0a3da6445cd298bc4a6b3aaa269075849c9510@linux.intel.com"},"message":"intel_sgx: driver for Intel Software Guard Extensions\n\nIntel SGX is a set of CPU instructions that can be used by applications to\nset aside private regions of code and data.  The code outside the enclave\nis disallowed to access the memory inside the enclave by the CPU access\ncontrol.\n\nSGX driver provides a ioctl API for loading and initializing enclaves.\nAddress range for enclaves is reserved with mmap() and they are destroyed\nwith munmap(). Enclave construction, measurement and initialization is done\nwith the provided the ioctl API.\n\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>\nTested-by: Serge Ayoun <serge.ayoun@intel.com>","distinct":true,"url":"https://api.github.com/repos/jsakkine-intel/linux-sgx/commits/38495105c3a518a37dd527f2756388f90557ede0"},{"sha":"a99e5bc8a66eedfd78afa7290ef920e7c137f71b","author":{"name":"Jarkko Sakkinen","email":"6e0a3da6445cd298bc4a6b3aaa269075849c9510@linux.intel.com"},"message":"intel_sgx: ptrace() support\n\nImplemented VMA callbacks in order to ptrace() debug enclaves. With\ndebug enclaves data can be read and write the memory word at a time by\nusing ENCLS(EDBGRD) and ENCLS(EDBGWR) leaf instructions.\n\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>\nTested-by: Serge Ayoun <serge.ayoun@intel.com>","distinct":true,"url":"https://api.github.com/repos/jsakkine-intel/linux-sgx/commits/a99e5bc8a66eedfd78afa7290ef920e7c137f71b"},{"sha":"9a6488fc06470b3f4d6689058ccf52b09c31c413","author":{"name":"Jarkko Sakkinen","email":"6e0a3da6445cd298bc4a6b3aaa269075849c9510@linux.intel.com"},"message":"intel_sgx: driver documentation\n\nDocumentation of the features of the  Software Guard eXtensions usable\nfor the Linux kernel and how the driver internals uses these features.\nIn addition, contains documentation for the ioctl API.\n\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>","distinct":true,"url":"https://api.github.com/repos/jsakkine-intel/linux-sgx/commits/9a6488fc06470b3f4d6689058ccf52b09c31c413"},{"sha":"5106a65bdd55a4f46cbdcff885562e39f1e6f09f","author":{"name":"Jarkko Sakkinen","email":"6e0a3da6445cd298bc4a6b3aaa269075849c9510@linux.intel.com"},"message":"intel_sgx: in-kernel launch enclave\n\nThe Launch Enclave (LE) generates cryptographic launch tokens for user\nenclaves. A launch token is used by EINIT to check whether the enclave\nis authorized to launch or not. By having its own launch enclave, Linux\nhas full control of the enclave launch process.\n\nLE is wrapped into a user space proxy program that reads enclave\nsignatures outputs launch tokens. The kernel-side glue code is\nimplemented by using the user space helper framework.  The IPC between\nthe LE proxy program and kernel is handled with an anonymous inode.\n\nThe commit also adds enclave signing tool that is used by kbuild to\nmeasure and sign the launch enclave. CONFIG_INTEL_SGX_SIGNING_KEY points\nto a PEM-file for the 3072-bit RSA key that is used as the LE public key\npair. The default location is:\n\n  drivers/platform/x86/intel_sgx/sgx_signing_key.pem\n\nIf the default key does not exist kbuild will generate a random key and\nplace it to this location. KBUILD_SGX_SIGN_PIN can be used to specify\nthe passphrase for the LE public key.\n\nThe CMAC implementation has been derived from TinyCrypt. The kernel\nAES-NI implementation is used for AES.\n\n[1] https://github.com/01org/tinycrypt\n\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>\nTested-by: Serge Ayoun <serge.ayoun@intel.com>","distinct":true,"url":"https://api.github.com/repos/jsakkine-intel/linux-sgx/commits/5106a65bdd55a4f46cbdcff885562e39f1e6f09f"},{"sha":"5c3baaad72e019f521808b02f03670359293d1d3","author":{"name":"Jarkko Sakkinen","email":"6e0a3da6445cd298bc4a6b3aaa269075849c9510@linux.intel.com"},"message":"intel_sgx: SGX_IOC_ENCLAVE_REMOVE_PAGES\n\nSGX_IOC_ENCLAVE_REMOVE_PAGES removes a range of pages by applying\nENCLS(EREMOVE). The use case for this is to dynamically remove pages\nfrom an enclave by first changing their type to TRIM and then applying\nthis ioctl. Removing trimmed pages keeps the enclave in a valid state.\n\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>","distinct":true,"url":"https://api.github.com/repos/jsakkine-intel/linux-sgx/commits/5c3baaad72e019f521808b02f03670359293d1d3"},{"sha":"b15b50638d45d133c84a1b8082ba50df433e2c38","author":{"name":"Jarkko Sakkinen","email":"6e0a3da6445cd298bc4a6b3aaa269075849c9510@linux.intel.com"},"message":"intel_sgx: SGX_IOC_ENCLAVE_MODIFY_PAGES\n\nSGX_IOC_ENCLAVE_MODIFY_PAGES modifies either the type or access rights of\nan enclave page by applying ENCLS(EMODT) or ENCLS(EMODPR) to a range of\npages. This moves the page to the pending state. The change takes effect\nonly after the enclave accepts it with ENCLU(EACCEPT).\n\nSigned-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>","distinct":true,"url":"https://api.github.com/repos/jsakkine-intel/linux-sgx/commits/b15b50638d45d133c84a1b8082ba50df433e2c38"}]}
{"actor":{"display_login":"jsakkine-intel"}}