initdata: update doc for digest usage #1991
Conversation
Add digest usage example in ibmse Signed-off-by: Qi Feng Huo <[email protected]>
huoqifeng
changed the title
| } | ||
| ``` | ||
|
|
||
| `se.user_data` is the HEX of the initdata digest string `52af3178dd7ad4bf551e629b84b45bfd1fbe1434b980120267181ae3575ea20ca9013b8eadf31d27eed7ff2552d500ef`. |
There was a problem hiding this comment.
can we give an example script on how to to convert 52af3178dd7ad4bf551e629b84b45bfd1fbe1434b980120267181ae3575ea20ca9013b8eadf31d27eed7ff2552d500ef to "353261663331373864643761643462663535316536323962383462343562666431666265313433346239383031323032363731383161653335373565613230636139303133623865616466333164323765656437666632353532643530306566"
There was a problem hiding this comment.
yeah, that's also not obvious to me. I thought initdata.digest hex was already a text representation? if not should we maybe write initdata.digest as raw bytes, so we avoid the double to_hex(to_hex(initdata_digest)) wrapping?
There was a problem hiding this comment.
Yeah, it's more reasonable to use the hash directly, I created a PR confidential-containers/trustee#462 in trustee to revise it.
Use initdata.digest directly rather than HEX in attestation policy Signed-off-by: Qi Feng Huo <[email protected]>
Add digest usage example in ibmse