As the title says, I'm trying to keep people from accessing certain Sub VI's that contain proprietary information in them. The majority of my code I would like to keep open source though. I have the pertinent information already segregated into the appropriate Sub VI's and now I just need to prevent other users from accessing the block diagrams. Any thoughts?
Thanks in advance.
Solved! Go to Solution.
I'd love to see a tutorial or video example of implementing this to wall off part of a vi in an existing project, including the experience for a non-access user who then inspects and runs code in the LabVIEW project. (Not an answer to your question, just expressing interest in it).
Just know that if the person trying to get access to this VI is persistent enough, he can crack the password (there is even a tool). Even NI agrees that password protection is not the best way and recommends removing block diagram whenever possible.
I would probably just build the "core"/propriety code into a Packed Project Library with debugging turned off, which should then not have any block diagrams, but still usable in the executable and the programming environment. You will need a separate project from your main one to build the PPL.
Even NI agrees that password protection is not the best way and recommends removing block diagram whenever possible.
I would be interested to read that article, can you link that here?