问题描述
如果有人知道 PHP 的 bcompiler 到底有多有效/安全/受保护，我很感兴趣 反对逆向工程.介绍页面大胆声明:
I'm interested if anyone knows exactly how effective/safe/protected PHP's bcompiler is against reverse engineering. The introduction page makes a bold claim:
在代码保护方面，可以肯定地说，如果没有随附的源代码注释，就不可能重新创建构建它的确切源代码.使用 bcompiler 字节码重新创建和修改类实际上是无用的.
也许关键词是精确"——如果你删除它，他们的说法有多真实?
Perhaps the key word is "exact" -- how true is their claim if you remove it?
PS - 请不要讲有关编译/混淆与许可的讲座.:)
PS - Please, no lectures about compilation/obfuscation versus licensing. :)
推荐答案
它就像将 C++ 编译为 ASM 一样安全.它可以通过仔细阅读和逻辑进行逆向工程或理解，并且可以编辑为，例如，添加 10 个硬币而不是 5 个非常容易.但是，即使是一小段字节代码也需要很长时间才能理解，并且原始源代码只能手工重写.在大多数情况下，变量名称等将无法恢复.
It is just as safe as compiling C++ to ASM. It CAN be reverse engineered or understood by careful reading and logic, and can be edited to, for example, add 10 coins instead of 5 very easily. However, it takes a long time to understand even a short piece of the byte code, and the original source code could only be re-written by hand. The variables names and such would be unrecoverable in most cases.
换句话说，PHP 是披萨食谱，字节码是热的新鲜披萨.您可以找到原始配方，但会花费很长时间，非常困难，而且您不会知道厨师的昵称是意大利辣香肠Roni".
In other words, PHP is the pizza recipe, the bytecode is the hot fresh pizza. You COULD find out the original recipe but it would take very long, be very difficult, and you would not know that the chef nicknamed pepperoni "Roni".
这篇关于PHP bcompiler 编码的代码有多安全?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！