保护源代码交付给客户 [英] Protect the source code on delivery to client

问题描述

我最近了解到，将要处理我们的核心产品之一的安装公司此前曾试图进行逆向工程供应商的工作邪恶目的。由于这一点，我想更多地了解如何保护我们的工作，到目前为止，我已经想好了以下内容：

I've recently learnt that the company that will handle the installation of one of our core products have previously tried to reverse engineer suppliers' work in evil purposes. Due to this I want to learn more about how to protect our work and so far I have thought of the following:

1），显然是使用混淆。问题是哪一个。

1) Obviously to use an obfuscator. Question is which one.

2）加密配置文件尽可能（尤其端点信息）。

2) Encrypt config files as much as possible (especially endpoint information).

3）将尽可能多的逻辑尽可能到Web服务的。

3) Move as much of the logic as possible to the web service.

4）使用SSL传输数据。

4) Use SSL for data transfers.

该项目是用C＃/ WPF和连接到托管在IIS 7我们与维克斯包装我们交付了一组Web服务，并WIX有什么规定？

The project is written in C#/WPF and connects to a set of web services hosted on a IIS 7. We package our deliveries with WIX, does WIX have anything to provide?

据我了解，在结束时，所有可执行文件可以被黑客入侵，并且作为一个次要的公司，我们也许应该专注于编写代码，而不是保护它。但这些小的步骤将在租赁使它更难。
还有什么可以做什么？难道社会上对本更多的建议？ 。链接到内部/外部资源，将不胜感激。

I understand that in the end all binaries can be hacked and that as a minor company we should probably concentrate on writing code instead of protecting it. But these minor steps will at lease make it harder. What else can be done? Does the community have any more advices regarding this? Links to internal/external resources would be much appreciated.

推荐答案

下面是你的选择：

• 请不要给他们的计划，他们已经滥用职权


• 让他们进入到一个许可协议，其中：
  
  
  
  • 他们可以逆向工程计划，甚至看到你的法律团队
  
  
  • 定义范围内的源代码，他们不能做任何事情没有邀请法律伤害
  
  

  这篇关于保护源代码交付给客户的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！