@paul_cardinale wrote:
@BertMcMahan wrote:
Forgive the off topic request but Paul could you expound on why that is?
The LV password protection is a lock, not an encryption. You can't get to a PW protected BD because the IDE respects the lock and won't let you in. But a VI always has access to its own BD, even if it's PW protected (essentially that VI is inside the secured area). When you inline a VI, that VI's code becomes part of the owning VI's BD. If property & invoke nodes were allowed, then an inlined VI could access the owner's BD, even if it were PW protected. Thus to break into a BD, you would only have to find a VI that's called by it, temporarily replace that VI on disk with a like-named inlined VI that opens the BD, then run the protected VI and voila, the BD opens.
If you get this working, I'm sure you can work around the PW in an easier way.
A quick fix would be the make the diagram property fail if it accesses a PW protected diagram, even if it is it's own diagram. I don't see a use case for it.
EDIT: BTW, I do agree that this is a plausible reason.