# 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:** 1\
**Showing post:** 3

<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.

---

_[View the full topic](https://forum.inductiveautomation.com/t/secured-non-text-python-script-for-deployment/51920)._