When using snphost fetch vcek, the generated VCEK URL returns a 500 Internal Server Error from the AMD KDS endpoint. This occurs even when the URL is correct and matches the format defined in the AMD VCEK specification.
Example:
https://kdsintf.amd.com/vcek/v1/<product_name>/<hwid>?blSPL=04&teeSPL=00&snpSPL=22&ucodeSPL=213
Both direct browser access and snphost attempts result in a 500 response, making it impossible to fetch a VCEK.
This appears to affect all VCEK fetch attempts across multiple platforms, not just a specific TCB level.
Expected:
A valid VCEK certificate response, or a clear error message indicating why the VCEK is unavailable.
Actual:
AMD KDS returns HTTP 500, and snphost cannot obtain a VCEK.
When using
snphost fetch vcek, the generated VCEK URL returns a 500 Internal Server Error from the AMD KDS endpoint. This occurs even when the URL is correct and matches the format defined in the AMD VCEK specification.Example:
Both direct browser access and
snphostattempts result in a 500 response, making it impossible to fetch a VCEK.This appears to affect all VCEK fetch attempts across multiple platforms, not just a specific TCB level.
Expected:
A valid VCEK certificate response, or a clear error message indicating why the VCEK is unavailable.
Actual:
AMD KDS returns HTTP 500, and
snphostcannot obtain a VCEK.