Even for non-scripts, the "protection" is only an impediment. Any designer can break that protection, and gain complete access. It was removed from Ignition v8+ because a "feature" that doesn't actually prevent IP theft is worse than simply not having it.
Some discussions for you to review:
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…
This post is just asking for an update on these issues:
Dumb Patenting Question
Best practice to prevent to stolen ignition resources
I'm concerned about protecting my intellectual property (IP) in Ignition projects. For now, I'm only looking at templates. Converting numerous templates into modules using the SDK is very much unfeasible.
Could you provide any updates on:
Enhanced Security Features: Plans to better secure scripts, templates, and resources?
Resource Encryption: Potential for …
2 Likes