Remember, Remember, forcing Secure Boot does not lock it to Windows 8 but signed software, sure a Linux distro won't use a grub loader cause of its crap license, but that means a bootloader with a different license can be used so everyone can sign it without sharing the key, though it sure has to actually support this UEFI Spec.
This is only true from the technical aspect. M$ has the possibility to sign the bootloaders that are allowed to run. Guess if an other but w8 ARM version will be allowed. And why do you consider grub to have a 'crap license'? Only because the rules claim for to reveal the private key in order to become signed? There would be a way to allow Linux based OSes, HTC for instance used closed source boot loaders to run a actually open OS, called Android. Due to massive complaints and a petition of the users they switched to a open loader again. M$ would simply need to sign a particular Android bootolader. Well it's up to the community such as XDA forums if they can manage to crack it. I don't see here a problem though. The consumer actually chooses his favorite OS when buying a phone / tablet. The one who has chosen an Android phone is not interested in to run another OS on it. Also the one who chooses a w8 phone will not be interested in to run Android on it. W8 and IOS are closed source OSes and will be / are restricted, so they can have a signed bootloader. HTC got complaints because Android is actually a open OS. There are people who simply want to modify their OS to style it and get most of it..... The situation of PCs is quite different. Nobody actually wants to have it locked down to w8 only. M$ would get massive complaints.
Microsoft confirms UEFI fears, locks down ARM devices By Aaron Williamson | January 12, 2012 softwarefreedom.org/blog/2012/jan/12/microsoft-confirms-UEFI-fears-locks-down-ARM
I will not buy a computer solely for Windows only. I will definitely complain vigorously to and against Microsoft. I am not sure it is even legal? Does Microsoft want second look by EU and US for anti-trust practices?
If and only if Microsoft will strictly implement the locking down of other operating system in Windows 8 ARM devices then do the reversed engineering, buy an Android tablet and load Windows 8 on it..
Simply don't buy a preinstalled PC / notebook. The entire restriction issues (whitelists also) are related to preinstalled PCs / notebooks which are assembled by one particular OEM. HP, Lenovo.......etc... I can understand that 'common' users buy a preinstalled OS, but every other user who is able to install the OS simply formats the drive to get rid of all that preinstalled bloat ware..... Well if it's right what 100 has quoted then even OA3.0 must have the option to disable secure boot, means any other OS can be used. Yeah, just ruin your device and bound it in chains...
Not sure if it'd be needed to emulate at all. BIOSes also have the MSDMTable. OEM activation for the masses will not be possible anymore due to unique keys.... ATM it seems OA3.0 will be OA2.1 plus the key stored at MSDM.....
Funny, you call something BS by using unconfirmed arguments. Even the requirement of secure boot at OA is not yet confirmed. If there will be OA devices that only run w8 is to expect at ARM devices for sure. Petar's opinion is as valid as yours....calling his concerns BS doesn't make yours better. He simply referred to a quoted source. An effort that will be not worth to make......
Yen, That is true. Hence I wrote that it takes time. The biggest problem with that remains if one can activate his/her system and that it stays activated. But it is an unlikely candidate for most people.
I've forgotten to mention. I've referred to venu's post (unlimited rearm) it is not worth the effort to 'find' another solution. To me either unlimited rearm or to perfectly mimic the activation are the only true methods, to mess with w8 itself can be only a temp. solution.....
Thanks Tito for the Intel download. ACPI MSDM table (offset 24h of the entire ACPItable where their data usually start right after the common table header): Structure: Offset: 0: version byte Offset: 8: type byte Offset: 10h: data length byte (1Dh = 29 digits) Offset 14h till end = serial data area = 29 hex digits (25 digits key plus 4 hyphens 2Dh) This we knew already and is now confirmed for sure.