F.A.Q - Python Script Protection (Obfuscate & Encrypt Python Source Code)

Python Script Code Protection

We are different in many ways. I'll list a few.

First, our obfuscation does not require any extra packages or modules for you to configure, download or figure out how to use in order to protect your python script. You just simply submit your code, and an obfuscated version of it will be generated. It's that straightforward.

Second, we support all versions of Python. And that means; no matter how complex your script is, if it is a valid python code, we can protect it. Yes, that is correct. Don't believe us? Well, contact us with a test case scenario :)

Third, we provide mechanisms through which you can easily track where your obfuscated python code is being used. Monitor the number of times attacks are being carried out on your protected python scripts.

Fourth, we understand there are many different ways a python project may be designed and as such, we have a very eager attitude towards fulfilling customization requests involving feature modifications and/or development.

Sure. Feel free to reach out to us at Support@EnScryption.com with a detailed description of your requirements.

Sure. Send us an email. Let us know which purchasing plan you're interested in. We'll find a suitable payment system for you to use.

Updated F.A.Qs / Latest News, Updates

Questions (compatibility,security,pyinstaller)

The enScrypt.io python code protection tool (pyenscrypt) can be used on any Ubuntu/Redhat/Linux based system and of course MacOSes.

  • Yes, the obfuscated python scripts protected on these systems will work on any OS python is available. Including Windows!

Yes, you can expect the encrypted python scripts to work wherever python is available. Linux, Windows...it does not matter!

Yes, you could. For your convenience, we actually include automated scripts for you to run to convert your encrypted scripts into either a binary or an executable. However, before deciding to add pyinstaller to the equation, it's important to revisit your personal reasons for code protection.

For instance, if your main objective is to ensure that your python code cannot be modified, ensure it is well protected and can't be easily hacked into, then, you don't need PyInstaller. The protection provided with our obfuscation tool is more than sufficient to satisfy that objective.

However, if your intention is to encrypt/obfuscate your python code, but also package all the modules used by your code into one binary or executable so that your users wont have to worry about getting, downloading, installing and configuring dependencies, then, yes, you could use PyInstaller for that.

Be aware though that, introducing pyinstaller into the mix means the execution time of the final script could be much higher than the unprotected version of it. But this may be irrelevant depending on your requirements.

No. We only require internet connectivity for the enScrypt.io Python Code Protection tool itself. The python code obfuscator.

Before proceeding to obfuscate any python script given to it to protect, our python obfuscator has to first validate itself with our servers. It essentially performs an handshake to confirm the authenticity of the copy you're using.

No. Your protected python script should be expected to work exactly as the original.

Yes. Currently, there's only two main levels of projection. Level 0 and Level 1. Level 0 provides the maximum security, but with this security comes added size to the encrypted script. This size is often insignificant. But should it ever become a concern, you can just switch to Level 1.

Level 1 provides the most basic, yet, powerful protection for your code. It is very light and with it, you can add or remove protection depending on the requirement at hand.

Latest How-to Videos on Python Code Protection

Questions (script size,execution time,licenses,plans)

The size of the encrypted script will be negligible, especially if encrypted using Level 1 protection.

Earlier versions of the encrypted scripts were much heavier, but over time, and with the feedback from several customers, we've been able to trim out the unnecessary parts.

Now, users get to choose specific levels of protection to apply to their scripts, as opposed to us imposing preset configurations.

No. One of the early challenges of protecting source code is developing the appropriate level of protection that does not noticesably impact the execution of the code being protected.

We are very proud to say that, as of June 19, 2021, scripts protected using our product can be expected to run almost as fast as their original / plain text versions. There will be time added to the execution of the final encrypted script, but this time is negligible.

But what exactly is 'negligible'? What does that mean?

We have quite a few very short, straight to the point videos in the above links available for you to watch to get an idea of what to expect. We hide nothing from you. Check out the videos and see for yourself.

Of course. During the duration of your license term, you get to choose when or if each script you protect should expire. If a script is protected without the expiration mandate, that essentially means the script will never expire. Your users will be able to continue using it for as long as they wish.

The online options requires you to upload your scripts to our online portal for them to be obfuscated and encrypted.

The on-prem options allow you to utilize the actual python code protection tool on your own private hosts. With this version, for the duration of the license period, you will be able to protect an unlimited number of python scripts on an unlimited number of servers.

Yes, the python scripts you encrypted during the period which the license was valid and current, will continue to work, even after your license expires. We don't control the expiration dates you assign to your scripts. That is completely up to you. You get to decide whether or not the script(s) you protect have to expire.