You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The computed PCR values at the end of the tpm2_eventlog YAML output can't be parsed correctly by YAML tools like the yq command line or online YAML formatters. The PCR hex values are transformed to float. It would probably be better to encode them as a strings by surrounding the hex values with double quotes. Tested with the current release 5.6 - 2023-11-08.
Sample output of tpm2_eventlog:
$ sudo ./bin/tpm2_eventlog /sys/kernel/security/tpm0/binary_bios_measurements
...
Event: |-
Exit Boot Services Returned with Success
pcrs:
sha256:
...
1 : 0x2e9a5e07140d956a059b65ef1af6c3c14079ca6f7220a0c0d6bdf1b0412a9a1d
...
The more I look into this, this is a jq bug. They actually roll their own parser with bison and flex. It never should choose float. Our work on next will correct all the YAML issues we have in a foolproof way, and provide a --canonical output that will output everything quoted as well as with type information.
The computed PCR values at the end of the tpm2_eventlog YAML output can't be parsed correctly by YAML tools like the yq command line or online YAML formatters. The PCR hex values are transformed to float. It would probably be better to encode them as a strings by surrounding the hex values with double quotes. Tested with the current release 5.6 - 2023-11-08.
Sample output of tpm2_eventlog:
Sample output, parsed by yq and other tools:
Expected output of tpm2_eventlog:
The text was updated successfully, but these errors were encountered: