.net native和obfuscation [英] .net native and obfuscation

查看:83
本文介绍了.net native和obfuscation的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

您好
我很高兴听到C#可以编译为本机代码。



我的启动产品是一个高级混淆器(实际上只是混淆),它读取(32位)X86原生机器指令。 更准确地说,它读取并生成ECOFF .obj文件。 与你的.net本机代码一起,
现在可以从c#源生成非常强大的防篡改代码。

有关详细信息,请参阅:  www.whitehawksoftware.com

 

- 当然我希望本机代码以.obj文件的形式生成。 (这样可以保护图书馆)

-与"一小部分编程"相关我可能会添加对.exe文件的支持,以防本机编译不会生成.obj文件。  (不是我想为我的创业公司付出额外的努力)

- 请你提供 尽可能多地提供有关本机代码的数据格式的信息,(我是一个bizspark成员)



我甚至可以想到这些好处可能是相互的: 强烈混淆的能力也可能为C#原生项目增加一些额外的价值。



鼓励和感谢,

Chris





Chris Jacobi

White Hawk软件的创始人(和洗碗机)

www.whitehawksoftware .com

chris@whitehawksoftware.com

jacobi@acm.org

Hi
I am excited to hear that C# can be compiled to native code.

My startup's product is a high-level obfuscator (Actally much more then just obfuscation) which reads (32-bit) X86 native machine-instructions.  More precise, it reads and generates ECOFF .obj files.  Together with your .net native code this should now enable generating very strong tamper-proof code from c# sources.
For details, see:  www.whitehawksoftware.com
 
-Of course I whish that native code is generated in form of .obj files. (So that libraries can be protected)
-With "a small matter of programming" I might add support for .exe files in case native compilation would not generate .obj files.  (Not that I would like such extra effort for my startup)
-Could you please provide  me with as much information as you can about whatever the data-format for the native code is/will be, (I am a bizspark member)

I could even think that benefits might be mutual:  The capability to strongly obfuscate might also add some extra value to the C# native project.

Encouragement and thanks,
Chris


Chris Jacobi
Founder (and bottlewasher) of White Hawk Software
www.whitehawksoftware.com
chris@whitehawksoftware.com
jacobi@acm.org

推荐答案

<你好Chris,

在.NET Native工具链的第一个开发者预览中,生成的本机代码直接生成一个.DLL,其中包含应用程序的本机代码,它使用的任何第三方库,以及应用程序所需的框架
部分。 虽然.DLL中的代码是标准的x64或ARM代码,但.NET Native二进制文件还需要一些额外的部分和代码才能正常工作。  例如,有一些信息编码为
使反射能够工作,并允许垃圾收集器与应用程序一起工作。

In this first developer preview of the .NET Native tool chain, the native code generated is produced directly into a single .DLL which contains the native code for the application, any 3rd party libraries it uses, as well as the portions of the framework that the application requires.  While the code in the .DLL is standard x64 or ARM code, there are a few extra pieces of and code that are also required for .NET Native binaries to work correctly.   For example, there is information encoded that enables reflection to work, and to allow the garbage collector to work with the application.

此时,此数据的编码(在我们开发产品时,甚至可能需要额外的数据和代码)仍然高度不变。  然而,随着我们在项目中取得进展,这些细节可能会最终落到我们能够使它们成为契约的
点。 我建议您在Microsoft dot com的dotnetnative上与我们联系,以便更详细地与我们的开发团队讨论您的工具

At this point, the encoding of this data (and even potentially what extra data and code is necessary) is still highly in flux as we develop the product.   However, as we progress in the project these details may wind up settling down to the point that we would be able to make them contractual.  I would recommend contacting us at dotnetnative at Microsoft dot com to discuss your tools with our development team in a bit more detail


这篇关于.net native和obfuscation的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆