WIP: talos testing

[Turnalek]

Summary & Motivation (Problem vs. Solution)

How I Tested These Changes

Pre merge check list

• Call out updates and breaking changes via conventional commits
• Communicate verification flow breaking changes especially thoroughly. If any of the following answers are no, then this is a verification flow breaking change:
  • Can enclaves in a previous QOS version still key forward to this new version?
  • Can previous versions of QOS verify attestations from this new version?
  • Can manifests generated by a previous version still be parsed by this one?
  • Can previous approvals still be verified against a manifest (i.e. is this a non-breaking change to the manifest signing payload)?
  • Can a previous version of QOS still perform a boot standard on an enclave of this version?

[james-callahan]

[root@i-0ae05a94158c48ece ales_talos_test]# ./qos_host --cid 16 --port 3 --vsock-to-ho│
st true --host-ip 127.0.0.1 --host-port 1234                                          │
Configuring vsock with VMADDR_FLAG_TO_HOST.                                           │[root@i-0ae05a94158c48ece ales_talos_test]# chmod +x qos_host
StreamPool start address: vsock cid: 16 port: 3                                       │[root@i-0ae05a94158c48ece ales_talos_test]# ../qos_client dangerous-dev-boot --host-
HostServer listening on 127.0.0.1:1234                                                │ip 127.0.0.1 --host-port 1234 --pivot-path ../signer-app.bin --restart-policy never
Sending ProtocolMsg bytes to enclave of len 9404629                                   │
START BYTES: 032300000044414E4745524F55535F4445565F42                                 │thread 'main' panicked at qos_client/src/cli/services.rs:1727:14:
END BYTES: 0000000001000000000000000000000000000000                                   │Unexpected response: ProtocolErrorResponse(InvalidPivotHash { expected: "473b70f3f49
Received ProtocolMsg bytes to enclave of len 138                                      │41a5763ff31efeb6fb124a21b8bf135f7f22026a362ccd0380195", actual: "a31e55f39839acc9dad
START BYTES: 0007400000003437336237306633663439343161                                 │fc27c89d7b7beab999aa8561b116a5e566244a9fed682" })
END BYTES: 3131366135653536363234346139666564363832                                   │note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
                                                                                      │[root@i-0ae05a94158c48ece ales_talos_test]#
──────────────────────────────────────────────────────────────────────────────────────┴────────────────────────────────────────────────────────────────────────────────────
Reaper::execute waiting for pivot and manifest                                                                                                                    [30/1844]
Reaper::execute waiting for pivot and manifest
Received ProtocolMsg bytes to enclave of len 9404629
START BYTES: 032300000044414E4745524F55535F4445565F42
END BYTES: 0000000001000000000000000000000000000000
-========PIVOT========
Received pivot bytes to enclave of len 9403048 and sha256: a31e55f39839acc9dadfc27c89d7b7beab999aa8561b116a5e566244a9fed682
START BYTES: 7F454C4602010100000000000000000003003E00
END BYTES: 0000000001000000000000000000000000000000
-=======/PIVOT========
Sending ProtocolMsg bytes to enclave of len 138
START BYTES: 0007400000003437336237306633663439343161
END BYTES: 3131366135653536363234346139666564363832
Reaper::execute waiting for pivot and manifest
Reaper::execute waiting for pivot and manifest
Reaper::execute waiting for pivot and manifest