PHP 5 软件作为商业产品
我在想 - 假设您投入了数千个工时并想出了一个最先进的 CMS 之类的东西。你如何确保从你那里得到它的人不会盗版？我可以坚持买家给我他们的 URL，然后我对其进行哈希处理，并将其用作软件中各处的校验和，但这听起来像是一种较弱的安全形式。
还有其他方法吗？一种可能是让客户在提供任何页面之前向我的服务器发送 POST 进行身份验证，但这听起来不公平。
（当然，我可以坚持自己托管该软件..）
I was thinking - say you are put thousand of man hours and come up with a state-of-the-art CMS or something. How do you ensure that whoever get it from you does not pirate it? I could insist the buyer to give me their URL and I hash it and use it as a checksum everywhere within the software, but that sounds like a weaker form of security.
Are there any other methods? One could be to have the customer to send a POST to my server for authentication before serving any pages, but that sounds unfair.
(Of course, I could insist on hosting the software myself..)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（5）
通常情况下，首选法律解决方案，而不是尝试寻找技术解决方案。使用合同和/或许可协议的法律框架，使客户无法尝试盗版或转售您的软件。
如果您的软件足够受欢迎，人们就会找到盗版它的方法（例如 Photoshop）。如果您的客户对与您的业务安排感到满意，那么他们不太可能通过盗版您的软件来破坏这一点。
Typically, instead of trying to find a technological solution to this problem, a legal solution is preferred. Using a legal framework of contracts and/or license agreements, make it unattractive for the customer to try to pirate or resell your software.
If your software is sufficiently desirable, people will find a way to pirate it (eg. Photoshop). If your customer is happy with their business arrangement with you, then they are unlikely to jeapordise that by pirating your software.
如果您要分发平台，通常会使用 Zend Guard 之类的平台。然而，这也意味着您的客户更难添加自己想要的修改。
现在很多软件都走 SaaS 路线，由制造公司自行托管。
也就是说，我会在这里回应其他答案的观点——让人们不想盗版你的产品（并激励他们不这样做）比尝试人们不这样做更好。
If you are distributing the platform, something like Zend Guard, typically. However, that also means it's harder for your customers to add in their own desired modifications.
A lot of software nowadays takes the SaaS route and is self-hosted by the companies that make it.
That said, I'd echo the sentiments of other answers here - it's better to make people not want to pirate your product (and give them incentives not to) than it is to try people to not do so.
仅为购买该软件的用户提供支持和升级。它并不能阻止复制它，但任何认真的用户都会购买它。
另一种选择是自己托管。但至少不要选择混淆路线。即使它不能完全阻止任何事情，但它会激怒您的忠实客户。
Provide support and upgrades only for those who have bought the software. It doesn't prevent copying it, but any serious users will buy it.
Another option is to host it yourself. But at least don't choose the obfuscation route. Even it won't exactly prevent anything, but it will irritate your loyal customers.
只是要钱。
我建议花更多的时间思考营销，而不是担心代码混淆。
我喜欢的一种方法是 jamroom.net 使用的方法。它们相当开放，向订阅者提供完整的代码，在某种程度上允许并鼓励更改/定制。没有浪费精力去混淆代码。
他们通过扩展、安装/维护/运营服务赚钱。我不知道他们过得怎么样。似乎围绕他们的产品建立了一个相当规模的社区。我所说的社区是指客户和第三方开发人员。这是一个额外的好处，他们的商业模型甚至可以扩展！
Just ask for money.
I would advise to expend more time thinking of marketing and less worrying about code obfuscation.
One approach I like is the one used by jamroom.net. They are fairly open, providing full code to subscribers, changes/customizations are allowed and encouraged to some extent. No efforts wasted on obfuscating code.
They cash-in with extensions, installation/maintenance/ops services. I don't know how well they fare. Seems that a respectable sized community builds around their product. By community I mean both customers and third-party developers. That's a bonus, their Biz model even scales!
与往常一样，Joe Blow Blogger 可能会盗版您的软件……但真正的商业客户不会承担这种法律风险。正如其他人所说，最好只为付费客户提供优质软件。打击盗版的最佳方式是通过社会和法律手段，而不是技术手段。
As always, Joe Blow Blogger may pirate your software...but real business customers aren't going to take that kind of legal risk. It's best, as others have said, to just provide quality software for your paying customers. Piracy is best combatted through social and legal means, rather than technological ones.