image-rs: get rid of checking decrypt_config
parameter
#523
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The high level API of image-rs is
pull_image()
. There is one parameter nameddecrypt_config
passed to the api, and the parameter is to specify the orignal kbc parameter, e.g.provider:attestation-agent:offline_fs_kbc:null
However, different parts of the parameter is now specified
attestation-agent
: the key to look up keyprovider is embedded inside the encrypted image layer annotation.offline_fs_kbc:null
: so-called AA_KBC_PARAMS, is defined in CDH if Kata-CC is used, so in this case, we do not to ensure the parameter is given as it will not be used. This is why we get rid of this parameter checking in this commit.In enclave-cc scenarios, the
decrypt_config
is still used, and we will check the parameter in concreteocicrypt-rs
'snative
key provider plugin.