This really applies to libkrun and reference-kbs. I feel it would be much easier if we'd force a user to supply a TeeConfig when wanting to run a confidential workload. I have a commit for libkrun that does exactly that, but I'd like some thoughts before I commit. This way, we wouldn't have to continually unwrap()Option<TeeConfig>s, as the case in which someone would like to run a confidential workload yet not supply a TeeConfig wouldn't make sense.
tylerfanelli
commented
1 year ago
cc @slp
This really applies to libkrun and reference-kbs. I feel it would be much easier if we'd force a user to supply a
TeeConfigwhen wanting to run a confidential workload. I have a commit for libkrun that does exactly that, but I'd like some thoughts before I commit. This way, we wouldn't have to continuallyunwrap()Option<TeeConfig>s, as the case in which someone would like to run a confidential workload yet not supply aTeeConfigwouldn't make sense.