LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How can I protect LabVIEW created application from having vi's extracted?

It seems that when you compile an exe with LabVIEW, an outside party can connect to it with VI Server and extract vi's from it.   There is a secret property you can enable in LabVIEW by adding "SuperSecretPrivateSpecialStuff=True" to the LabVIEW ini file which allows you to convert a VI Ref to a binary buffer. You can write that binary file to disk as a VI.

 

Presumably you can extract any VI within the EXE from any LabVIEW created exe which allows you to access VI server via TCP.  

 

We can disable VI server in the INI file, but, of course a hacker could just turn it on again before launching our application.

 

So our only plan at this point is to have the application look at its environment and see if VI Server over TCP/IP is enabled and if so turn it off or shut down the application. Furthermore we would continue to do so as the application runs.

 

Anyone have any better ideas?

0 Kudos
Message 1 of 5
(3,289 Views)

Remove the block diagram from the vi.

 

https://www.ni.com/docs/en-US/bundle/labview/page/removing-block-diagrams-from-vis.html

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 2 of 5
(3,265 Views)

@RTSLVU wrote:

Remove the block diagram from the vi.

 

https://www.ni.com/docs/en-US/bundle/labview/page/removing-block-diagrams-from-vis.html


That has nothing to do with built executables.

 

My advice is to disable the debugging.  All that should be in the executable then should be the compiled code.



There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 3 of 5
(3,247 Views)

@crossrulz wrote:

@RTSLVU wrote:

Remove the block diagram from the vi.

 

https://www.ni.com/docs/en-US/bundle/labview/page/removing-block-diagrams-from-vis.html


That has nothing to do with built executables.

 

My advice is to disable the debugging.  All that should be in the executable then should be the compiled code.


If you buid the exe with vi's that have their block diagrams removed would this not remove the block diagrams from the exe?

 

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 4 of 5
(3,237 Views)

The default for an exe has the block diagram automatically removed so the link does not apply.

You can also use the third-party license toolkit - https://www.ni.com/en/support/downloads/tools-network/download.third-party-licensing-and-activation-...

0 Kudos
Message 5 of 5
(3,229 Views)