On Tue, 7 Apr 2020, Lukasz Hawrylko wrote:
Unfortunately, this bug is not reported anywhere. In real life scenarios
I don't see any benefits of loading multiple SINITs. In most cases you
have one SINIT that is dedicated to the platform.
After a closer inspection this might be a different bug as the reboot
occurs also if I specify only one SINIT module, the file
6th_gen_i5_i7_SINIT_71.BIN.
Why does tboot think that this file is a valid SINIT module for this CPU
and try to use it? Is this a bug in the ACM module or tboot? Is there some
algorithm for choosing the correct SINIT module?
-Timo
_______________________________________________
tboot-devel mailing list
tboot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tboot-devel
