Obfuscation isn't difficult in most programming languages. It's why we have "good practices" because it is so easy to hide what you mean in badly written code.
Obfuscation tends to be even easier in dynamic languages because of how forgiving they tend to be - and because they tend to give you direct access to the environment so that you can manipulate it.
Today, for fun, I'm going to obfuscate this code:
def _(n):
if n <= 0:
I've had some fun ruining Python recently, but Python is what I use at work. I prefer to use other languages when I'm doing stuff for fun.
And obfuscation only really makes sense in fun and competition - given a suffeciently determined actor, your code will be reverse engineered. Unless you write it in Malboge.
For this particular experiment, I'll be using Lua 5.3. As I'll probably need to dive into some of the less portable functions to commit our atrocities, I can't guarantee it will run on other popular versions like Luajit or 5.1.
| import re | |
| from io import StringIO | |
| from decimal import Decimal | |
| # TODO: | |
| # - investigate: late column casts better than early? (make temp table all text?) | |
| # - encoder/decoder for all django field types | |
| # - sanitize method interfaces of CopyConverter / more django-like | |
| # - Do we need a temp file shim instead of StringIO for very big data? | |
| # - Better with ByteIO instead of StringIO? |
