.NET混淆DLL：我如何保护我的代码？ [英] .NET obfuscation of a DLL: how can I protect my code?

问题描述

我正在和一家小公司探讨合作伙伴关系。该公司正在寻找可以提高利润的算法，并且我有一些可以帮助他们的原型软件。我的软件的核心是非常保密的，如果公司掌握它，那么他们肯定不会需要我。我绝对会和他们签订合同，我将有法律保护，但我仍然希望尽可能多地保护他们之间的保护层和我的商业秘密。

$ b $我可能需要与开发人员密切合作，将我的算法自动化并将其集成到系统中，但是我想在DLL中提供核心功能，所以我可以保护我的商业秘密，但仍然有能力与他们的开发人员合作。考虑到我的情况，混淆是否值得？还有其他合理的选择吗？

解决方案

我不知道这是否是您的选择，但您可以考虑提供算法作为使用 WCF 或 Xml-rpc 或 REST 或某事。当然， HTTPS ，

这样他们可以使用算法，但是他们永远不会得到你的代码。

只要算法不需要太多的往返或大量的数据传输。也就是说，只要该算法不需要实时地使用< 100ms左右。

I'm in the process of exploring a partnership with a small company. The company is looking for an algorithm that can improve their profits and I have some prototype software that can help them. The core of my software is very confidential and if the company gets a hold of it, then they will certainly not need me. I'm definitely going to sign a contract with them and I will have legal protection, but I still want to put as many protective layers between them and my "trade secret" as possible.

I might have to work close with their developers to automate my algorithm and integrate it in their system, but I want to offer the core functionality in a DLL so I can protect my "trade secret", yet still have the ability to work with their developers. Is obfuscation worth it given my situation? Are there other reasonable alternatives?

解决方案

I don't know if this is an option for you, but you might consider providing the algorithm as a web service using WCF or Xml-rpc or REST or something.

With HTTPS, of course.

That way they can use the algorithm, but they can never get at your code.

Should work as long as the algorithm doesn't require too many round trips or huge amounts of data being transfered. Which is to say, as long as the algorithm doesn't need to be used in real time with a responsiveness of < 100ms or so.

这篇关于.NET混淆DLL：我如何保护我的代码？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！