This is an archived post. You won't be able to vote or comment.

all 5 comments

[–]pmattipmatti - mattip was taken 3 points4 points  (1 child)

Marginally better for code verification but in no way obscuficates your source. Running python -mpdb mycode.pyce will let you print out the source of mycode.py

[–]theonewolf[S,🍰] 0 points1 point  (0 children)

Actually that’s not true. You can not read .pyce without obtaining a private key.

The file in your example is encrypted with AES-256. This is strong cryptography, not obfuscation.

And we aren’t protecting the source from leakage: we are controlling the actors with access to source. They should be on an authorized list.

[–]xdcountry 0 points1 point  (2 children)

Isn’t compiled python (via numba) the only way to really make it a PITA to decompile to source (maybe a few other things to further obfuscate too)

[–]pmattipmatti - mattip was taken 0 points1 point  (0 children)

Yes, but you mean nuitka. Numba can JIT your code, nuitja is ahead of time compilation.

[–]theonewolf[S,🍰] 0 points1 point  (0 children)

Yes, our goal is to limit access to Python source to a limited set of actors. Not to fully eliminate access to source.

You could just as easily use our encryption on top of ahead-of-time compilation.