hyperledger-labs
Better handling of IAS v3 extensions
IAS v3 handled new return status CONFIGURATION_NEEDED and additional headers "Advisory-URL" and "Advisory-IDs". The advisory-* headers should give pointers on how to address these errors (e.g., CONFIGURATION_NEEDED might appear now due to L1TF if HT is enabled). Probably a good idea to also handle other error messages by at least passing them explicitly into logs rather than just a generic error message?
Yes, even now that we moved to IAS v4. There are multiple statuses that could be retuned by IAS and that may be considered in the verification of proof data -- or of the verification report in general. Some of these have been handled while testing CCF-based PDO on Azure in HW mode.
