发布商业 PHP 代码。你混淆或编译它吗？还是直接按原样交付？
可能的原因：
1）因此用户无法弄清楚代码并“向自己颁发更多许可证”或其他对您具有商业敏感性的内容
2）因此用户无法“仅进行微小的更改”并破坏他所要做的事情不明白，然后告诉你他没有改变任何东西并希望你修复它（当然，你可以让他付钱，但首先更容易避免麻烦）
3）所以客户不能接受你的一些软件并用它来开发新产品
4) 你不好意思让你的未注释的意大利面条代码被人看到;-)
5) 还有吗？
你一般做什么？你是如何做到的？
Possible reasons:
1) so the user can't figure out the code and "issue himself more licenses" or other stuff that is commercially sensitive to you
2) so the user can't "just make a tiny change" and break what he doesn't understand, then tell you he didn't change anything and expect you to fix it (sure, you can make him pay, but it's easier to avoid the hassle in the first place)
3) so the customer can't take some of your software and use it do develop new products
4) you are embarrassed to let your uncommented spaghetti code be seen ;-)
5) any more?
What do you generally do? And how do you do it?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（6）
如果无法在您的服务器上托管 php 代码，那么最好的办法就是简单地提供具有限制性许可证的源代码并接受您上面概述的风险。如果用户“颁发更多许可证”并且违反了您的条款，您可以采取法律行动。
If hosting the php code on your servers is not an option, the best thing is to simply deliver the source code with a restrictive license and accept the risks you outlined above. If the user "issues more licenses" and it violates your terms, you can pursue legal actions.
在接收端，我购买了使用 ionCube PHP Encoder (http://www.ioncube.php) 进行压缩/编码的 PHP 软件。 com/）。它需要添加额外的服务器组件，并在我们的服务器上包含有效的闭源代码，而我们的 IT 团队对此都不满意。但它阻止了我们像您尝试那样摆弄来源。
On the receiving end, I have purchased PHP software that was ofsucated/encoded with ionCube PHP Encoder (http://www.ioncube.com/). It required adding an additional server component and including effectively closed-source code no our servers, neither of which our IT team was happy about. But it prevented us from fiddling with the source as you are attempting.
我按原样交付。最终用户希望能够编辑代码，无论是免费的还是商业的。他们中的大多数人都不是盗版者，因此妨碍他们只会损害您的业务（不太满意的客户 = 更少的积极提及和推荐）。无论如何，无论您是否对其进行混淆/编码，盗版者都会窃取您的软件。
I deliver it as is. End-users expect to be able to edit the code whether it's free or commercial. Most of them aren't pirates, so getting in their way will just hurt your business (less happy customers = less positive mentions and referrals). The pirates will steal your software whether you obfuscate/encode it or not, anyway.
如果客户破坏了我的代码并试图将其固定在我身上，我会提议将代码恢复到最后一个已知的工作配置。这通常会结束对话，因为他们知道这是他们所做的修改。
对我来说似乎是不必要的预防措施。即使您对其进行混淆，它仍然可以重新分发。作为开发人员，盗版是一种已知的风险，避免盗版的最佳方法是发布开源软件。 :)
如果我购买了一个被混淆的脚本（使我很难做出更改），我会认真考虑将来与开发人员开展业务。我的意思是..什么 PHP 脚本需要零修改才能让它完全按照你想要的方式做？
If a client breaks my code and try to pin it on me I offer to restore the code to the last known working configuration. This usually ends the conversation because they know it was a modification they made.
Seems like an unnecessary precaution to me. Even if you obfuscate it it can still be redistributed. As a developer, piracy is a known risk and the best way to avoid it is to release software that is open source. :)
I would seriously think twice about doing business with a developer in the future if I purchased a script that was obfuscated (making it difficult for me to make changes). I mean.. what PHP script needs ZERO modification to get it to do exactly what you want it to?
关于第 2 点：
您始终可以生成可交付成果的哈希值。非常简单的方法：使用源文件作为输入生成 md5 哈希值。如果您在接到支持电话时怀疑被篡改，只需对部署的文件进行哈希处理即可确定您的客户是否篡改了代码，并尝试让您修复他们的混乱情况。
这是非侵入性的（您只需在交付之前进行哈希处理，并将哈希值保留在文件中），并且是检查文件内容的一种非常安全的方法。
Concerning point #2:
You can always generate a hash of your deliverables. Very simple method: generate an md5 hash using the source files as input. If you suspect tampering when receiving a support call, simply hash the deployed files to figure out if your client has tampered with the code and tries to get you to fix their mess.
This is non-intrusive (you just hash before you deliver, and keep the hashes in your files) and a quite safe way to check the contents of your files.
没有人提到过，提供许可源允许客户将其关闭并拥有无限的许可。这是我主要关心的问题
No one has addressed that delivering the licensing source allows customers to switch it off and have unlimited licences. That is my main concern