Intel® SGX Data Center Attestation Primitives
Attestation is the process of demonstrating that a software executable has been properly instantiated on a platform. Intel® SGX attestation allows a remote party to gain confidence that the intended software is securely running within an enclave on an Intel® SGX enabled platform.
- Added Ubuntu 20.04 support.
- Added Intel® Provisioning Certification Service V3 API support for ECDSA attestation.
- Fixed bugs.
- Intel® Xeon® E Processor based Server
- Intel® SGX option enabled in BIOS with the Flexible Launch Control support
Supported Linux* OS distributions:
- Ubuntu* 16.04 LTS 64-bit Desktop and Server version
- Ubuntu* 18.04 LTS 64-bit Desktop and Server version
- Ubuntu* 20.04 LTS 64-bit Desktop and Server version
- Red Hat* Enterprise Linux* Server 8.2 (for x86_64)
- CentOS 8.2 64bits
Note: It is highly recommended to use the listed Linux* OS distributions. Other distributions have not been tested.
KNOWN ISSUES AND LIMITATIONS
- Provisioning Certificate Caching Server (PCCS) in Intel® DCAP 1.9 release only support Provisioning Certification Service (PCS) V3 API. If you want to use previous PCS API version such as V2, please use PCCS in previous DCAP release.
- In order to make DCAP 1.9 software stack work with previous version PCCS, please configure correct PCCS URL in Quote Provider Library (QPL) configuration file, make sure the PCCS version number is also lower than 3. For sample, “PCCS_URL=https://localhost:8081/sgx/certification/v2/”
- During the current release we have learned that the DKMS infrastructure uses the driver version as an arbitrary string and not as a numeric value. As a result, installing an old version on top of a new version will work, moreover, when more than one version is installed and a kernel update occurs there is no guarantee that the new version will be used in the new kernel – apparently either of the existing versions may be used To address these issues, the 1.10 driver installer will uninstall a previously installed driver if exists.
Note: The uninstall may fail if the driver is in use by an enclave or the AESM, in this case the user will be notified and will be required to manually uninstall the driver.