oak icon indicating copy to clipboard operation
oak copied to clipboard

Decide on approach when the trusted runtime receives invalid data from the untrusted launcher

Open conradgrobler opened this issue 2 years ago • 1 comments

Some examples include:

  • Invalid lengths/indices in the used elements of a virtqueue
  • Invalid vsock packet lengths
  • Invalid lengths for custom framing and object serialisation

We could ignore bad data, send an error, or terminate the VM. We might have different approaches for different types of invalid data.

conradgrobler avatar May 25 '22 17:05 conradgrobler

Also related, we should decide what to do when the communication channel is closed/broken. We could try to re-establish, or just shut down the VM.

conradgrobler avatar May 26 '22 07:05 conradgrobler