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

Windows Store apps can be in .NET, C++, or JS.

Reply Parent Score: 3

BluenoseJake Member since:
2005-08-11

This affects desktop apps, not store apps. Because desktop apps are Win32 apps, they aren't compiled to run on ARM.

Reply Parent Score: 2

chithanh Member since:
2006-06-18

Because desktop apps are Win32 apps, they aren't compiled to run on ARM.
But they can be compiled to run on ARM, and with the exploit now they will run.

This is of course not interesting for commercial software vendors, but people who want to build Win32 desktop apps for the Surface RT now have the ability to.

Reply Parent Score: 3

Nelson Member since:
2005-11-29

Unsigned Windows Store apps have always been able to run (using the aforementioned Remote Debugger) which also allows you to use the full .NET/Win32 API in your apps for pure sideloading.

This facet of the Windows App sandbox is enforced only at Submission time by running the Windows App Certification Kit.

Its always been the case. And has therefore always been possible to run unsigned code for your own purposes on your own device (As I've been tirelessly saying for months, but which people conveniently ignore in their criticisms).

I just tested it and fired up an C++ app which uses a Win32 API (that also fails the App Certification static analyzer) and can be successfully deployed to my Surface RT.

Reply Parent Score: 3

ze_jerkface Member since:
2012-06-22

Windows Store apps can be in .NET, C++, or JS.


Please stop spreading this myth.

.NET and C# are not the same thing.

Microsoft is not allowing .NET applications in Windows RT. C# is a supported language but without .NET that means existing applications have to be re-written in WinRT.

It's total bullshit really and an insult to .NET developers. Everything is expected to be re-written except Microsoft's software that gets access to the secret .NET/Win32 stash.

Reply Parent Score: 1

Nelson Member since:
2005-11-29


Please stop spreading this myth.

.NET and C# are not the same thing.


I'm well aware, and there is no myth.


From MSDN: (http://msdn.microsoft.com/en-us/library/windows/apps/br230302.aspx


The .NET Framework provides a subset of managed types that you can use to create Windows Store apps using C# or Visual Basic. This subset of managed types is called the .NET for Windows Store apps and enables .NET Framework developers to create Windows Store apps within a familiar programming framework


And since you obviously are misinformed, here's a white paper for you to read: CLR and the Windows Runtime (http://go.microsoft.com/fwlink/p/?LinkId=243099)


Microsoft is not allowing .NET applications in Windows RT. C# is a supported language but without .NET that means existing applications have to be re-written in WinRT.


No. Microsoft supports .NET . It just supports the CoreCLR profile of the 4.5 BCL. That's a limited subset.

It also doesn't include WPF, WinForms, or any other things that wouldn't make sense for the Windows Store.

The BCL is there, the execution engine, IL, the JIT compiler, everything is there.


It's total bullshit really and an insult to .NET developers. Everything is expected to be re-written except Microsoft's software that gets access to the secret .NET/Win32 stash.


You want to know what's an insult to .NET developers? Your complete and utter ignorance on this subject matter.

The Windows Runtime and XAML stacks are for the most part native code. However, the WinRT projection library and some clever .NET Interop at compile-time manages the glue between WinRT and .NET pretty efficiently. A lot more efficiently than COM RCWs or P/Invoke.

You not understanding this only speaks to your ignorance as a .NET developer.

I shouldn't even have to be saying this, if you want a primer on the Windows Runtime (and judging by your sorry excuse for a comment, you need one) you can read the MSDN documentation.

Your blind, irrational, hatred for Windows 8 does not entitle you to your own facts.

Edited 2013-01-08 06:32 UTC

Reply Parent Score: 3