-
Notifications
You must be signed in to change notification settings - Fork 279
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
Recreating FULL 12Mb ROM image from Lenovo downloaded, neutered+deactivated xx30 ME exe #327
Comments
@corna: any insight playing with the CI produced coreboot.rom? |
@corna: actually this output shows that coreboot doesnt integrate gbe.bin at all in coreboot. |
@corna: Could we fix that by randomizing it? Could me_cleaner extract Gbe + me + ifd, minimizing what is linked to a host computer (remove IFD OEM host related information in IFD, generalizing it) and randomize Gbe mac address? Would you be interested in being funded to do such work? The ME update.exe contains full ME, preextracted IFD and Gbe from a preexisting rom works but should be anonymized. The last coreboot.rom artifact still gives the same result when trying to reapply me_cleaner on it, even though ROM is completely functional including Gbe blob:
I guess there is some misaligments between IFD and real regions, but can't spot it. |
@corna : updates here following official Intel doc:
|
Gbe generated I and included in maximized roms for a while. Closing |
Hello there,
Attempting to bridge the legal gap/inertia in creating full 12mb reproducible Heads ROM images.
I realized recently that:
This shows some inconsistencies, resulting in the full ROM not containing a vaild GBe region, since the result as if Gbe region was not included.
ifdtool -d on the extracted ifd.bin shows the same result as when asking a dump on the whole generated coreboot.rom on this commit
Resulting full ROM image is still resulting in e1000e not probing ethernet card correctly while me_cleaner still complains when ran against downloaded ROM regions being invalid. Any insight?
The text was updated successfully, but these errors were encountered: