mirror of https://github.com/clearlinux/graphene.git synced 2026-08-24 07:55:52 +00:00

Files

T

Michał Kowalczyk 3d31f2d18d Introduce one, central manifest, zero-config children and constant MRENCLAVE

This is the next part of the great loader rework, with a lot of breaking changes:

- Complete removal of the "trusted children" thing - now children
  processes can be spawned arbitrarily and from arbitrary mountpoint
  types, without any additional configuration needed.

- There's a new, required option in the manifest: `libos.entrypoint` - it
  specifies the URI to the entry binary in the first process. There's no
  need anymore to name the manifest and the first binary identically.

- On SGX, the main binary is not measured in MRENCLAVE anymore - only
  PAL, LibOS and the manifest are measured. This is enough to bind
  MRENCLAVE to a specific entrypoint user executable if wanted - it
  just has to be mounted as a trusted file.

- All Graphene SGX enclaves have now exactly the same MRENCLAVE. This is
  a hash of a "Graphene stub", which can "fork" into one of two states
  in runtime: initial process or child. The initial process creates a
  new "Graphene namespace" with a clean state, it can also be attested
  remotely (contrary to child processes). The initial process can spawn
  children processes by spawning a Graphene stub and directing it to
  start in the child mode. It then attests it locally, and if
  successful, establishes an encrypted pipe, "connects" to its own
  namespace and treats as trusted (including sending protected files
  key).

- Now, there's only one, central manifest describing the initial state
  of a Graphene instance which can be spawned from it (previously, each
  process required a separate manifest which could have different
  configuration - which wasn't actually supported and didn't make sense
  design-wise). One downside of central manifests is that all processes
  require the same enclave configuration (e.g. size), but that was
  already the case so far because of broken checkpointing code. Also,
  this is only a temporary problem, which will cease to exist after the
  introduction of EDMM.

- `sgx.static_address` was renamed to `sgx.nonpie_binary` and now has to
  be inserted manually by users (`sgx_sign` tools doesn't know about the
  binaries run inside, which can be even provided or generated in
  runtime by the user's workload).

- Caveat: the memory gap for non-PIE executables was removed because it
  requires adding a new option to the manifest to be cleanly
  implemented. This is left for some future loader rework PR.

2021-01-12 19:53:24 +01:00

1.0 KiB

Raw Permalink Blame History

Running Node.js express server with Graphene SGX

This is a Node.js application, runs an express server, listening on a given port.

Environment

This application was tested with Node.js version 8.

Prerequisites

This project requires Node.js to be installed. See https://nodejs.org/ for more details on how to install Node.js.

Run npm install, which installs all dependencies and modules needed for this application. See package.json for more details on Node.js dependencies needed for this project. At this point, the application itself can be executed without Graphene by running node helloworld.js.

Steps to run without SGX

Run make.
Run ./pal_loader nodejs helloworld.js 3000.
The expected output should be the following: Example app listening on port 3000!

Steps to run with SGX

Run make SGX=1 in order to build the application using SGX.
Run ./pal_loader SGX nodejs helloworld.js 3000
The expected output should be the following: Example app listening on port 3000!

1.0 KiB Raw Permalink Blame History