Dmitrii Kuvaiskii
91e882c130
RA-TLS integrates Intel SGX remote attestation into the TLS connection setup. Conceptually, it extends the standard X.509 certificate with SGX-related information. The additional information allows the receiver (verifier) of the certificate to verify that it is indeed communicating with an SGX enclave (attester). RA-TLS is shipped as three libraries: - ra_tls_attest.so: creates self-signed RA-TLS X.509 certificate with SGX quote embedded; typically linked into server apps. - ra_tls_verify_epid.so: verifies RA-TLS certificate by sending SGX quote to IAS and verifying attestation report from IAS; typically linked into client apps. - ra_tls_verify_dcap.so: verifies RA-TLS certificate by providing SGX quote v3 to the libsgx_dcap_quoteverify library and relying on its assessment of the quote; typically linked into client apps. This commit also adds an RA-TLS example using simple mbedTLS server and client. The server generates the RA-TLS certificate, and the client connects to the server, verifies this certificate, and performs a dummy HTTP request. This example is added to Jenkins.
Example Integrations
This folder contains application integration examples.
For instructions how to build and run each application under Graphene, please see the README or README.md in each subdirectory.
How to Contribute?
Please put your application sample in a subdirectory with a comprehensible name. Ideally, the subdirectory name should be the same as your application. In addition, your application sample should have the following elements:
-
README.md: Please document the tested environment and instructions for building and running the application. If your application sample has any known issues or requirements, please also specify them in the documentation. -
Makefile: Users should be able to build your application sample by running themakecommand. If your application needs extra building steps, please document them in theREADME.md. In addition, we ask you to provide sufficient comments in theMakefileto help users understand the build process. If your application also runs on Graphene-SGX, please include the commands for signing and retrieving the token in theMakefile. -
Manifest(s): Please provide all the manifests needed for running your application sample. Do not hard-code any user-specific path or personal info in the manifests. The ideal way is to create manifest templates that contain variables to be replaced by runtime options in
Makefile. See other subdirectories for examples of the manifest templates. We also ask you to provide sufficient comments in all the manifests to help users understand the environment. -
Sample inputs and test suites: If you have any inputs and test suites for testing the application, please provide them in the same subdirectory, too.
Please do not include any tarball of source code or binaries in the
application samples. If an application requires downloading the source
code or binaries, please provide instructions in the README.md, or
download them automatically and verify the checksums as part of the
build process.