Linked by Thom Holwerda on Sun 6th Jan 2013 23:00 UTC
Windows "It's taken longer than expected but it has finally happened: unsigned desktop applications run on Windows RT. Ironically, a vulnerability in the Windows kernel that has existed for some time and got ported to ARM just like the rest of Windows made this possible. MSFT's artificial incompatibility does not work because Windows RT is not in any way reduced in functionality. It's a clean port, and a good one. But deep in the kernel, in a hashed and signed data section protected by UEFI's Secure Boot, lies a byte that represents the minimum signing level." Good stuff. Very good stuff.
Thread beginning with comment 547684
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[7]: Seems like a lot of work
by Nelson on Mon 7th Jan 2013 17:59 UTC in reply to "RE[6]: Seems like a lot of work"
Member since:

Its a reality to expect to have to take such measures because Win32 moving forward is of limited strategic importance to Microsoft, as such, it is unlikely that they relent on their position.

So if a company *really* wants to run their full fledged Desktop app on Windows RT, this is the only avenue they have.

Not that its a good solution. Its much better to just sideload a Windows Store app without restrictions (as I've mentioned in one of my comments below) because you get integration with the new lifetime process manager for free.

Reply Parent Score: 2