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
Hi, I am studying the loading procedure of TDX module,
Based on the SDMs, I found that ensuring the initial integrity of P-SEAM loader (which is loaded into the SEAM Range) is the key to protect following modules (e.g., TDX module, TDVMs).
Also, I read that NP-SEAM loader (authenticated by Intel) is responsible to load the P-SEAM loader.
However, aren't there any possibility that untrusted BIOS loads its own compromised P-SEAM loader and finalizes SEAM Range by configuring SEAMRR MSRs?
Is there any hardware mechanism that prevents untrusted BIOS from writing SEAMRR MSRs?
I could not find any information from the SDMs.
The text was updated successfully, but these errors were encountered:
Thank you for showing interest in our TDX technology.
P-SEAM Loader can only be loaded by NP-SEAM Loader and both are part of the same Intel signed binary. Intel’s SEAM architecture prevents loading a non-Intel P-SEAM Loader.
Hi, I am studying the loading procedure of TDX module,
Based on the SDMs, I found that ensuring the initial integrity of P-SEAM loader (which is loaded into the SEAM Range) is the key to protect following modules (e.g., TDX module, TDVMs).
Also, I read that NP-SEAM loader (authenticated by Intel) is responsible to load the P-SEAM loader.
However, aren't there any possibility that untrusted BIOS loads its own compromised P-SEAM loader and finalizes SEAM Range by configuring
SEAMRR
MSRs?Is there any hardware mechanism that prevents untrusted BIOS from writing
SEAMRR
MSRs?I could not find any information from the SDMs.
The text was updated successfully, but these errors were encountered: