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 547671
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Seems like a lot of work
by Nelson on Mon 7th Jan 2013 15:26 UTC in reply to "RE[4]: Seems like a lot of work"
Nelson
Member since:
2005-11-29

It's probably a bad business plan to base your app on a vulnerability in the base OS, but hey, that's just my way of thinking.


That's just reality. The Windows Runtime is the future of Windows, and Windows RT is the direction that Microsoft is headed in. I don't believe the transition will be complete until WinRT completely replaces Win32, but it will eventually happen.

This blog post is insightful and sheds a lot of light on their strategy: http://hal2020.com/2013/01/02/there-is-no-arm-in-windows-rt/

Reply Parent Score: 2

BluenoseJake Member since:
2005-08-11

WinRT and This hack have nothing do with each other. This is a hack to allow unfettered access to the desktop, It doesn't have anything to do with the app store, WinRT or Metro.

Reply Parent Score: 2

Nelson Member since:
2005-11-29

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

ze_jerkface Member since:
2012-06-22

I don't believe the transition will be complete until WinRT completely replaces Win32, but it will eventually happen.


Win32 will never be replaced. It will be here as long as computers exist.

There are millions of lines of Win32 that no one even understands. The people who wrote them are all dead or retired. Do you want to go step through black box code that helps a machine process ore? Of course not which is why Win32 isn't going anywhere. Even if Microsoft went tits up Win32 be duped and supported. Win32 is needed more by society than Microsoft.

Reply Parent Score: 3

Nelson Member since:
2005-11-29


Win32 will never be replaced. It will be here as long as computers exist.

There are millions of lines of Win32 that no one even understands. The people who wrote them are all dead or retired. Do you want to go step through black box code that helps a machine process ore? Of course not which is why Win32 isn't going anywhere. Even if Microsoft went tits up Win32 be duped and supported. Win32 is needed more by society than Microsoft.


Sorry, but judging from your last comment, I refuse to even acknowledge you have a shred of insight on anything pertaining to this topic.

Legacy will likely remain in Windows 8, but Windows RT is unmistakably Microsoft's OS moving forward.

Sure, many, many years down the line there will be an incarnation of Windows that ships with Win32, but it won't be consumer facing.

Microsoft is positioning the Windows Runtime as the replacement for Win32, and by forcing Windows Store apps to only use the Windows Runtime, it is guiding developers through that transition gradually.

You not being able to see the tea leaves doesn't really matter.

Reply Parent Score: 3