你应该看看getdropbox.com的人是如何为他们的客户端软件(包括Linux)做这件事的。这是相当棘手的破解，需要一些相当有创意的拆卸来通过保护机制。

取决于客户是谁，一个简单的保护机制，结合合理的许可协议将比任何复杂的许可/加密/混淆系统更有效。

最好的解决方案是将代码作为服务出售，比如托管服务，或者提供支持——尽管这并不总是可行的。

以.pyc文件的形式发布代码可以防止你的保护被一些#所破坏，但这几乎不是有效的反盗版保护(就像有这样的技术一样)，而且归根结底，它不应该达到任何与公司签订像样的许可协议所能达到的效果。

专注于让你的代码尽可能好用——拥有满意的客户会让你的公司赚更多的钱，而不是防止一些理论上的盗版。

用同样的方法保护c/c++的二进制文件，即对可执行文件或库二进制文件中的每个函数体进行混淆，在每个函数项的开头插入指令“跳转”，跳转到特定的函数来恢复混淆的代码。字节码是Python脚本的二进制代码，所以

首先编译python脚本代码对象 然后迭代每个代码对象，将每个代码对象的co_code混淆如下所示

    0   JUMP_ABSOLUTE            n = 3 + len(bytecode)

    3
    ...
    ... Here it's obfuscated bytecode
    ...

    n   LOAD_GLOBAL              ? (__pyarmor__)
    n+3 CALL_FUNCTION            0
    n+6 POP_TOP
    n+7 JUMP_ABSOLUTE            0

将混淆的代码对象保存为.pyc或.pyo文件

那些模糊的文件(。Pyc或.pyo)可以被普通的python解释器使用，当这些代码对象第一次被调用时

First op is JUMP_ABSOLUTE, it will jump to offset n At offset n, the instruction is to call a PyCFunction. This function will restore those obfuscated bytecode between offset 3 and n, and put the original byte-code at offset 0. The obfuscated code can be got by the following code char *obfucated_bytecode; Py_ssize_t len; PyFrameObject* frame = PyEval_GetFrame(); PyCodeObject *f_code = frame->f_code; PyObject *co_code = f_code->co_code; PyBytes_AsStringAndSize(co_code, &obfucated_bytecode, &len) After this function returns, the last instruction is to jump to offset 0. The really byte-code now is executed.

有一个工具Pyarmor可以通过这种方式混淆python脚本。

在某些情况下，可以将软件(全部或至少关键部分)移动到组织托管的web服务中。

这样，许可证检查就可以在您自己的服务器机房的安全环境中执行。

发布.pyc文件有它的问题-它们与创建它们时使用的python版本以外的任何其他python版本都不兼容，这意味着您必须知道产品将运行的系统上运行的python版本。这是一个非常有限的因素。

“有没有解决这个问题的好办法?”不。没有什么可以防止逆向工程。甚至DVD机器上的固件也被逆向工程，AACS加密密钥被暴露。这还是不顾DMCA规定的刑事犯罪。

由于没有任何技术方法可以阻止客户阅读您的代码，所以您必须应用普通的商业方法。

Licenses. Contracts. Terms and Conditions. This still works even when people can read the code. Note that some of your Python-based components may require that you pay fees before you sell software using those components. Also, some open-source licenses prohibit you from concealing the source or origins of that component. Offer significant value. If your stuff is so good -- at a price that is hard to refuse -- there's no incentive to waste time and money reverse engineering anything. Reverse engineering is expensive. Make your product slightly less expensive. Offer upgrades and enhancements that make any reverse engineering a bad idea. When the next release breaks their reverse engineering, there's no point. This can be carried to absurd extremes, but you should offer new features that make the next release more valuable than reverse engineering. Offer customization at rates so attractive that they'd rather pay you to build and support the enhancements. Use a license key which expires. This is cruel, and will give you a bad reputation, but it certainly makes your software stop working. Offer it as a web service. SaaS involves no downloads to customers.