Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Logging component #120

Open
spernsteiner opened this issue Oct 2, 2024 · 1 comment
Open

Logging component #120

spernsteiner opened this issue Oct 2, 2024 · 1 comment
Assignees
Milestone

Comments

@spernsteiner
Copy link
Collaborator

The logging component should receive telemetry from the autopilot via MAVLink and log some of the values (such as current GPS position) to disk.

@spernsteiner spernsteiner self-assigned this Oct 2, 2024
@spernsteiner
Copy link
Collaborator Author

From in-person discussion with @podhrmic:

  • 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.

@podhrmic podhrmic added this to the MVP 1.0 milestone Nov 8, 2024
spernsteiner added a commit that referenced this issue Feb 14, 2025
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants