You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The logging component should connect to the autopilot telemetry port and record some or all telemetry values to disk.
Logs should be saved in text format, with a timestamp on each line.
Logs will be encrypted by storing them on an encrypted filesystem (exact filesystem type TBD). The key for the encrypted filesystem will be obtained from the Mission Key Management component ([FEATURE] Implement Mission Key Management (MKM) component #98). The filesystem should be initialized on first use if possible.
trusted_boot infrastructure for guest VMs
This branch provides infrastructure to allow using trusted_boot inside the various OpenSUT guest VMs. In particular, the logging component (#120) needs this so it can get an attestation when requesting a key from the MKM.
This has a few parts:
* Build the `trusted_boot` binary and install it into the guest VMs
* Provide systemd units that wrap `opensut_boot` (the `vm_runner` binary that mounts and runs the application image) in `trusted_boot`, so both `opensut_boot` and the application can access the trusted boot daemon
* Update `calc_measure.py` and record the measure of the `opensut_boot` binary to allow computing expected measures for applications
The logging component should receive telemetry from the autopilot via MAVLink and log some of the values (such as current GPS position) to disk.
The text was updated successfully, but these errors were encountered: