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
FIPS204 requires using SHA512 for pre-hash mode to maintain security level at category 5. IETF Composite Keys and Signatures draft requires using SHA512 for hybrid mode between ML-DSA-87 and ECC Secp384r1.
Hence, HMAC384 needs to be updated to HMAC512 to maintain PQC flow at category 5. HMAC384 will be removed.
Since HMAC512 requires 512-bit key, UDS and FE needs to be extended to 512 bits.
KV needs to be extended to 512 bits as mentioned here: #580
Since PCR path needs to be implemented within hardware boundary, any IETF requirement for hybrid signature will be hardcoded.
The text was updated successfully, but these errors were encountered:
We support dual signatures, and FW/SW will be responsible for using composite signature or any other hybrid schemes
HMAC supports both HMAC384 and HMAC512.
PCR path will be addressed as a part of #645
FIPS204 requires using SHA512 for pre-hash mode to maintain security level at category 5.
IETF Composite Keys and Signatures draft requires using SHA512 for hybrid mode between ML-DSA-87 and ECC Secp384r1.
Hence, HMAC384 needs to be updated to HMAC512 to maintain PQC flow at category 5. HMAC384 will be removed.
Since HMAC512 requires 512-bit key, UDS and FE needs to be extended to 512 bits.
KV needs to be extended to 512 bits as mentioned here: #580
Since PCR path needs to be implemented within hardware boundary, any IETF requirement for hybrid signature will be hardcoded.
The text was updated successfully, but these errors were encountered: