Python Code Obfuscation [closed]

Each Answer to this Q is separated by one/two green lines.

Do you know of any tool that could assist me in obfuscating python code?

Your problem space is underspecified. Is this for a command-line app? Is this code supposed to be used as a library?

In addition to the two other answers, you could embed the code into a binary. When it starts, decode the code and eval the string. This works for a shared library extension as well. You could also do that with byte code, I think, but it wouldn’t be as simple as calling Py_EvalCode.

py2exe or freeze are other solution, which convert the code into an executable. It just includes the code in the binary, and doesn’t do any sort of serious obsfucation, but it’s still harder than opening a .py file.

You could write the code in Cython, which is similar to Python and writes Python extension files in C, for use as a .so. That’s perhaps the hardest of these to reverse engineer and still give you a high-level language for develoment.

They are all hackable, as are all solutions. How hard to you want it to be?

I actually found a very nice project which basically converts a Python to C++ and create a binary, statically linked file.

Check this out:

In many situations you can ship byte-compiled .pyc files instead of the .py source files. This gives you some level of obfuscation. As the pyobfuscate README suggests, this has limitations. But you may be able to combine the two approaches.

Python’s standard library includes You can run this on a directory and it will generate .pyc files for all your source files. The .pyc files will only include bytecode and docstrings, and will strip out all comments. You could then copy this directory, and then run something like rm -rf $(find . -name .py) to remove the original source files.

Your best bet is to compile it using Shed Skin, an experimental Python-to-C++ compiler.

Although it doesn’t do obfuscation, this Python recipe works very well for minimizing the size of Python code, including stripping out comments.

The answers/resolutions are collected from stackoverflow, are licensed under cc by-sa 2.5 , cc by-sa 3.0 and cc by-sa 4.0 .