预防代码盗窃 - Chaperon 或类似的东西
有人听说过Chaperon吗？它能有效防止代码被盗吗？
现在我明白，如果有人要窃取代码，可以有很多方法，而且没有什么是完全万无一失的，所以请不要给我这个答案。
我想知道这有多有效以及该实用程序/软件到底如何工作？
还有其他类似的工具吗？
Has anyone heard of Chaperon? is it effective in preventing code theft?
Now i understand that there can be many ways if someone was to steal code and there is nothing that could be completely foolproof, so please don't give me this as an answer.
I want to know how effective this is and how does this utility/software exactly work?
Are there any other tools that are similar to this one?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
这是一个错误的问题。请参阅云中的安全协作软件开发环境
为什么您会这样做想和你不信任的人一起工作吗？组织控制以使其有效所需的成本是如此之大，以至于您的效率太低而无法在市场中生存。
Chaperon没有太多竞争的原因很简单，就是没有市场。开始使用它，很快就会倒闭。
It is the wrong question to ask. See Secure collaborative software development environment in the cloud
Why would you want to work with people you don't trust? The costs of organizing the control needed to make that effective are so large that your efficiency would be too low to survive in the market.
The reason that Chaperon doesn't have much competition is simply that there is no market. Start using it, go out of business fast.
在实施任何“代码盗窃预防”方案时，需要考虑的一件重要事情是，您愿意用生产力换取安全性。创建和调试代码最高效的环境是开放且易于共享的环境。这就是为什么每年都会编写数百万行开源代码，尽管大多数参与其中的人都没有获得报酬。
仔细考虑开发人员时间方面增加的开销和成本是否值得，理论上您的开发人员可能会盗窃您的算法和架构，并且如果确实值得的话，他可能会重新创建代码偷窃。
现在，保护您的源代码存储库免受外部访问，并保护“传输中”的代码免遭开发组外部可能窃取代码的人的侵害，这实际上可以归结为网络安全，您最好将其发布在 serverfault 上.com 或 superuser.com
One strong thing to consider when implementing any "code theft prevention" scheme is the fact that you're willingly trading productivity for security. The most productive environment for creating and debugging code is an open and easily shared one. This is why there are millions of lines of Open Source code written every year, even though most people involved aren't being paid for it.
Consider carefully whether the increased overhead and costs in terms of developer time is worth the theoretical potential for theft by one of your developers, who is already familiar with your algorithms and architecture, and could probably re-create the code if it was really something worth stealing.
Now, protecting your source code repositories from external access, and protecting your code "in transit" from people external to your development group who might be stealing it really boils down to Network Security, and you'd probably be better off posting it on serverfault.com or superuser.com
您无法有效地完成您所要求的事情，尤其是在您不信任在那里工作的人员的环境中。
正确的解决方案是建立一个在其他人获得软件时仍然稳健的业务模型。如果正如您所说“职业道德不可靠”，那么无论如何您都应该指望该软件会得到传播。
不要依赖软件的人为稀缺性——特别是如果，正如你所说，你不能相信你的员工能够维持这种稀缺性——相反，要依靠成为最了解软件的人。
You can't effectively do what you're asking, especially in an environment where you don't trust the people working there.
A proper solution is to build a business model that is robust in the face of someone else getting the software. If as you say the “work ethics are unreliable”, you should count on the software getting spread around anyway.
Don't rely on artificial scarcity of the software – especially if, as you say, you can't trust your staff to maintain that scarcity – instead, rely on being the people who know the most about it.
我认为在这种情况下能做的就是监控。防火墙网络。拒绝 https 流量。所以用户无法安全上传。拥有在插入外部 I/O 设备时发送电子邮件/记录日志的软件。
如果可以的话，解雇你不能信任的人。
I think all that can be done is monitor in situations like this. Firewall network. Deny https traffic. So users can not securely upload. Have softwares that email/log when external I/O devices are plugged.
Fire people whom you cant trust if that is an option.