How WinRT Metro Style HTML5 / JavaScript Applications Are Packed And Protected

Question

I am just wondering how HTML5 / JavaScript Metro applications will be packaged and protected against cancellation.

For Ill packaging, expect some kind of signed zip / jar (not to mention .appx on MSDN), but for protection, outside of the heavy mess for JavaScript. I can't imagine any other way (maybe a new precompiled / binary format?)

If the protection is not very good, too much IMHO will not develop when writing HTML5 / JavaScript applications.

Answer 1

Instead of just crypto learning, another option is to implement proprietary algorithms / logic inside a third-party WinRT component. This way you can be sure that your own algorithm is protected by compilation. If you decide to implement in .NET, there is an opportunity for someone to reverse engineer it.

The idea is to write your client in JS / HTML5, apparently, it will be somewhat simple if you do not have huge patented information. Then you write your WinRT component in C # / C ++, which contains your own "Sausage Production Process". You call this WinRT component to create some “sausage” with some data entry. This approach means that your secret recipe for Sausage is safe, but at the same time provides you with the simplicity of the platform.

Is this an acceptable solution?

Answer 2

I wondered the same thing, and I agree that cryptocurrency training will be key, of course, in the early days of protecting metro-style applications.

it is obvious that all code will be carefully reviewed on the MS side before it is offered for download, even confusing code using code scanning tools. I think how well this works until it’s visible. I am sure that in the previous days there will be problems with hiccups and security problems.

there is a fairly detailed safety guide that mentions "safety rails", etc., which sound pretty interesting.

http://www.microsoft.com/download/en/details.aspx?id=27408

rob ganly