Provided a reproducible SDK.
Supported new OS: RHEL 8.1, CentOS 8.1 and Fedora 31.
Supported user to specify platform id in PCK Cert ID Retrieval Tool’s command line option.
Added ability to execute Platform Cert ID Retrieval Tool on multi-package platforms without
loading enclaves. PCCS now supports this functionality. The platform still needs to support
SGX.
Updated Platform Cert ID Retrieval Tool and Multi-package registration tool to align with BIOS
platform manifest changes.
Added .deb and .rpm installers for Platform Cert ID Retrieval Tool and Multi-package
Registration Agent.
Fixed bugs.
Signed-off-by: Li, Xun <xun.li@intel.com>
Simulation libraries are provided through the SDK installation into
the sdk_libs directory and the environment file adds that directory to
LD_LIBRARY_PATH. Starting in version 2.8 new simulation libraries were
introduced but not added to this path.
This commit adds libsgx_quote_ex_sim.so, libsgx_epid_sim.so, and
libsgx_launch_sim.so to the expected directory.
Without this change applications following the conventions of the sample
Makefiles may build but fail to execute.
Signed-off-by: Dan Middleton <dan.middleton@intel.com>
The current upstream candidate driver users /dev/sgx/enclave and
/dev/sgx/provision files. Add the device files to aesmd systemd service
file so that they can be accessed.
Signed-off-by: Ismo Puustinen <ismo.puustinen@intel.com>
Some developers may have workstations that are not Intel
based. These developers should be able to test their enclaves
with the SGX simulation before building real SGX enclaves and
running those enclaves on genuine Intel processors.
By fixing CPU feature detection, developers with non-Intel
workstations can use SGX simulation to develop SGX enclaves.
Signed-off-by: Seth Moore <sethmo@google.com>
This commit updates the commands one should use when verifying that
they've properly built the SDK and/or have the SGX properly set up,
up and running.
It turns out that the executable for the samples is
generated inside a `bin` subdir (located in each sample), and it is
imperative to run the sample directly from that dir as otherwise
one will be greeted with `failed to load enclave`-like error.
Signed-off-by: Jakub Konka <jakub.konka@golem.network>
* Fix sgx-gdb throw exceptions on every ocall in Rust-SGX
In Rust-SGX environment, `sgx-gdb` always throws exception after ocall:
```
Python Exception <class 'gdb.error'> syntax error in expression, near `)0x7fffffffd840 = 0'.:
```
And the debugger stops immediately. At this time, the debugger is working in `Rust` mode instead of `C` mode:
```
gdb-peda$ set *(uintptr_t *)0x7fffffffd6d0 = 0
syntax error in expression, near `)0x7fffffffd6d0 = 0'.
gdb-peda$ set *(u32)0x7fffffffd6d0 = 0
syntax error in expression, near `0x7fffffffd6d0 = 0'.
gdb-peda$ p sizeof(u32)
$4 = 0x4
gdb-peda$ show language
The current source language is "auto; currently rust".
gdb-peda$ set language c
gdb-peda$ set *(uintptr_t *)0x7fffffffd6d0 = 0
gdb-peda$
```
This PR helps set the language to `c` before execution of essential gdb commands, and rolls back to `auto` afterwards. This would benefit lots of developers who are developing SGX enclaves in other languages.
Signed-off-by: Yu Ding <dingelish@gmail.com>
* Fix