all Windows 8 OEM need UEFI ?

ANSWER TO BOCH:
Table is decrypted and windows reads it. You could use a loader to load an already decrypted table, but secureboot will prevent the loader from running because it's not signed.
Non OA3.0 machines don't have the decryption key/mechanism build in. We also can't mod the UEFI to include either
- a custom module with decrypted table and loading mechanism
- a custom module with encrypted table and decrypting + loading mechanism
cause in both the 2 cases the digital cert of UEFI or the modules don't match with the data anymore.

SOME THOUGHTS AFTER WRITING ABOVE STUFF:
Again I'm only speculating now about something I thought about when writing the above.
OA3.0 requires UEFI 2.3.1. So that probably means that any 2.3.1 ALWAYS checks it's own signatures. This prevents us from adding custom tables and modules to it. It's obvious then that windows checks if you are indeed running 2.3.1 cause otherwise you can't have OA3.
So If we mod an UEFI lower than 2.3.1 (2.3.0 for example) that doesn't check it's own signatures, we can add stuff to it without any problem. We might even use a loader and stuff to emulate a TPM. When the UEFI is modded in that way that windows thinks it's 2.3.1 and it looks like it has secureboot enabled (while it hasn't), windows has no reason to think the emulated TPM chip and loaded tables aren't valid.

Of course this still brings no solution for non OA3 machines that already come with 2.3.1, it works only for UEFI versions that don't include signature checking or where it can be turned off.

 

Windows could check the certificate that is used by UEFI. If it is revoked then it can go to non-legit.

 

You need to login to view this posts content.

 

It also seems that OEM's need to send a list back to Microsoft to pre-activate those systems. Even when we create al those factors in a loader (or something like that), the result might still be an non-activated system. The key question remains what the Digital Product Key is going to be. The same thing as we have seen before like the OEM-SLP keys or totally different keys as stated by DAZ?

 

Hmm... If they are really requiring a TPM, I wonder how they are gonna handle countries that legally restrict the use of it (including China and Russia, which aren't exactly small markets).

 

I found this info while doing some reading, could be of use / interest .

 

I guess that Microsoft is using the data supplied by the OEM to pre-activate all those OEM-systems. The consumer buys the system. When the system has done it's setup, it goes online and fetch it's activationcode. Microsoft then knows which OEM-system is activated and can supply it to the OEM. They also can verify if it is a real sold OEM-system. After that they can spot "fake" activated OEM-systems and deactivate them.

But then again this is just my guess.

 

I have worked out a little more of what is going on in the 16D0A23E-C09C-407D-A14A-AD058FDD0CA1 module
a lot of time is devoted to correcting the OEMID, OEMTableId to match the MSDM, also the CreatorID, OEMRevison
and CreatorRevision is also updated with hard coded values. CreatorID is changed to "MSFT" or "AMI " RSDT is changed
to "MSFT" some other tables are changed to "AMI ".

later in the code a "PCMP" table is built and installed in low memory by the EFI_LEGACY_BIOS_PROTOCOL the comment's
in LegacyBios.h indicated that this memory region can be ether the 0xE0000->0xEFFFF or 0xF0000->0xFFFFF which is
normally write protected.

then an empty MP table is built, a pointer to the PCMP is added and then it is also installed in low memory with EFI_LEGACY_BIOS_PROTOCOL

I have not worked out what data is added to the PCMP.

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Don't panic too much since at this point its all speculation as to what the final protection is going to be.

There good deductive reasoning going on but tell ms makes windows 8 final we wont have a true concrete answer.

Also when been down this route before with windows supposedly being uncrackable and its cracked in very short order.

I have no doubts its going to be cracked within short order.

The other side of this is windows 8 final could bite and no one would want it anyway...lol

Interesting reading this though lots of brain power.

 

Indeed.
With Yen, nononsence and others, it appears there is a lot of relevant and very well presented information regarding UEFI and OA3.0.

Thanks to all!

 

if we remember, in win7 time also there were lot of speculation about strong activation method in OA 2.1 but immediate after lenovo leak the activation tool was ready..lets see MDL experts are already on the way of finding the methods to bypass the activation or still in search of finiding what this OA 3.0 is all about and how it works..but finally fact is man made can be break by another man...its just a matter of time..keep your fingers crossed...

thanks to all the BIOS mod experts here...keep it going and keep compress and decompress