另一种让代码更难被窃取的方法是使用jython，然后使用java混淆器。

这应该工作得很好，因为jythonc将python代码转换为java，然后将java编译为字节码。因此，如果混淆了类，就很难理解反编译后会发生什么，更不用说恢复实际的代码了。

jython的唯一问题是你不能使用用c编写的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.

无论是Cython还是Nuitka都不是答案，因为当运行用Nuitka或Cython编译成.pyd或.exe文件的解决方案时，会生成一个缓存目录，所有的.pyc文件都会复制到缓存目录中，因此攻击者可以简单地反编译.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脚本。

我记录了如何通过将其转换为.so文件和将其转换为python轮文件来混淆python: https://github.com/UM-NLP/python-obfuscation

你的雇主是否意识到他可以“偷”回其他人从你的代码中得到的任何想法?如果他们能读懂你的作品，你也能读懂他们的。也许看看你如何能从这种情况中受益，会比担心你可能会失去多少，获得更好的投资回报。

[编辑]回答尼克的评论:

没有得到也没有失去。客户得到了他想要的东西(因为他自己进行了更改，所以已经为此付费了)。因为他没有发布变更，就好像它没有发生在其他人身上一样。

现在如果客户出售软件，他们必须更改版权声明(这是非法的，所以你可以起诉并且会赢->简单的案件)。

如果他们不更改版权声明，第二级客户就会注意到软件来自您的原创，并想知道发生了什么。很有可能他们会联系你，这样你就会了解到你的作品被转售的情况。

同样，我们有两种情况:原来的客户只卖了几份。这意味着他们并没有赚到多少钱，所以为什么要麻烦呢。或者是销量。这意味着你有更好的机会了解他们的工作，并为此做些什么。

But in the end, most companies try to comply to the law (once their reputation is ruined, it's much harder to do business). So they will not steal your work but work with you to improve it. So if you include the source (with a license that protects you from simple reselling), chances are that they will simply push back changes they made since that will make sure the change is in the next version and they don't have to maintain it. That's win-win: You get changes and they can make the change themselves if they really, desperately need it even if you're unwilling to include it in the official release.