Expand description
Core components and logic for QOS. This contains both the logic for the process running in the enclave and exports for use by secure apps and QOS clients
§Maintainers Notes
This crate should have as minimal dependencies as possible to decrease supply chain attack vectors and audit burden
Modules§
- cli
- CLI for running an enclave binary.
- client
- Streaming socket based client to connect with
crate::server::SocketServer. - handles
- Logic for accessing read only QOS state.
- io
- Abstractions for low level I/O.
- parser
- Command line token parser.
- protocol
- Quorum protocol
- reaper
- The Reaper is responsible for initializing the enclave’s primary processes. Concretely it spawns the enclave server and launches the “pivot” executable once it becomes available in the file system.
- server
- Streaming socket based server for use in an enclave. Listens for connections
from [
crate::client::Client].
Constants§
- DEFAULT_
SOCKET_ TIMEOUT_ MS - Default socket connect timeout in milliseconds
- EPHEMERAL_
KEY_ FILE - Path to Ephemeral Key.
- MANIFEST_
FILE - Path to the Manifest.
- PIVOT_
FILE - Path to Pivot binary.
- QUORUM_
FILE - Path to Quorum Key secret.