# 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:** 2

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

---

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