Updates the config file to accept a [char; 4] instead of a u32 for the key symbol signature. This is to better match the SIGNATURE_32 function provided by edk2, which converts 4 characters into a u32 signature.
[ ] Impacts functionality?
Functionality - Does the change ultimately impact how firmware functions?
Examples: Add a new library, publish a new PPI, update an algorithm, ...
[ ] Impacts security?
Security - Does the change have a direct security impact on an application,
flow, or firmware?
Description
Updates the config file to accept a [char; 4] instead of a u32 for the key symbol signature. This is to better match the SIGNATURE_32 function provided by edk2, which converts 4 characters into a u32 signature.
How This Was Tested
Locally confirmed a config file and efi/pdb are successfully parsed.
Integration Instructions
N/A