-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SIE error #414
Comments
Hi @quic-pansing, Thank you for testing with latest ACS image, would need some more information to debug the issue faced,
|
HI @amrathesh , The SIE test suite is has few test which is modifying/tampering the existing DB and then if there is reset invoked in subsequent test , due to mismatch DB, device failed to load the image . test case : Verify signed DB append update (pass) reboot test case: Runtime services test: Test MOR and MORLOCK log: DxeImageVerificationLib: Image is signed but signature is not allowed by DB and SHA256 hash of image is not found in DB/DBX. expectation: Regards, |
Hi @smangali-qc, Thank you for the detailed clarification. The test cases which tamper/modify KEK/dB/dBX restores them to ACS keys shipped with the image (used for initial key provisioning) by calling SecureBootVariableCleanup function [1][2]. Given that all variable update SCT tests passed, we shouldn't be observing the above issue. I acknowledge a bug in the bbr-acs codebase where SecureBootVariableCleanup was not called for individual checkpoints, and a direct return was invoked instead, which might lead to wrong db values. I have raised a patch for the same[3], review and merge is awaited. [1] VariableUpdatesBBTest.c#L161 Regards, |
Hi @smangali-qc, We have fixed the bug mentioned in previous reply, please build latest Systemready ACS and give a fresh run on SUT and share if it fixed the issue your are facing. Thanks and Regards, |
Hi @quic-pansing , @smangali-qc, Please share any updates on this, after testing with latest SystemReady ACS build which includes above mentioned fixes. Thanks and Regards, |
issue is still not fixed.. we are checking if we can fix, will propose change |
continue with #400
issue still exists on latest ACS 3.0, but olderv version do not have this issue. @amrathesh
The text was updated successfully, but these errors were encountered: