# Secured (non-text) python script for deployment

**URL:** <https://forum.inductiveautomation.com/t/secured-non-text-python-script-for-deployment/51920>\
**Category:** Ignition\
**Tags:** security, python, scripting\
**Created:** [October 14, 2021, 1:26am UTC](https://forum.inductiveautomation.com/t/secured-non-text-python-script-for-deployment/51920 "2021-10-14T01:26:49Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![user5](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/user5/32/39393_2.png) [@user5](https://forum.inductiveautomation.com/u/user5)\
**Post date:** [October 14, 2021, 1:26am UTC](https://forum.inductiveautomation.com/t/secured-non-text-python-script-for-deployment/51920/1 "2021-10-14T01:26:49Z")

</div>

Hello,

We are extending the functionality in Ignition UI with Python scripting, some or most of it could be considered IP and we do not want our customers to be able to read the files.

So far what we have seen is that all python scripts are text files.

Is there a way to use something like pyinstaller or PYC which deploys in non-text file?

Thanks in advance.

---

<div class="post-metadata">

**Author:** ![bmusson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/bmusson/32/87530_2.png) [@bmusson](https://forum.inductiveautomation.com/u/bmusson)\
**Post date:** [October 14, 2021, 1:56am UTC](https://forum.inductiveautomation.com/t/secured-non-text-python-script-for-deployment/51920/2 "2021-10-14T01:56:35Z")

</div>

Not really.

See this forum post and its discussion for more details.

> [@Best practice to prevent to stolen ignition resources](https://forum.inductiveautomation.com/t/best-practice-to-prevent-to-stolen-ignition-resources/44344/):
>
> Hi, As system integrator, there are some cases that I like to protect my resources in ignition after delivering project to client. For example creating a library that use resources like python lib and views,… In other SCADA packages I can put password and encrypted the resource. The resource can be used by system but can’t modify by others unless they know password. The protect option in ignition doesn’t work because when other can access to gateway config they can change the role and passwo…

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [October 14, 2021, 2:16am UTC](https://forum.inductiveautomation.com/t/secured-non-text-python-script-for-deployment/51920/3 "2021-10-14T02:16:51Z")

</div>

No. Your best bet for obfuscation is to provide functionality via custom module instead.

Note my use of “obfuscation” - that’s all it will ever be. You cannot prevent a moderately determined user from getting your IP as long as they have physical or virtual access to the gateway machine.

---

<div class="post-metadata">

**Author:** ![andrews](https://avatars.discourse-cdn.com/v4/letter/a/898d66/32.png) [@andrews](https://forum.inductiveautomation.com/u/andrews)\
**Post date:** [October 31, 2021, 5:30am UTC](https://forum.inductiveautomation.com/t/secured-non-text-python-script-for-deployment/51920/4 "2021-10-31T05:30:07Z")

</div>

I think this stuff is kind of dumb no offense. Any decent programming company can do whatever 10 different ways