06-29-2006 09:14 AM
06-29-2006 02:45 PM
06-29-2006 02:51 PM
@nutmegzzzz wrote:
(I wish I could find the web site now and give credit because they had a lot of interesting labview programs)
If you just look at context help, you get the name "Michale Aivalotis". I quick google search leads me to this.
06-29-2006 02:58 PM
07-25-2016 03:43 AM
Hi
What length of the password it can crack?
07-25-2016 04:05 AM
07-25-2016 09:40 AM
It can crack a password of ANY length ... But it takes a billion years.
07-25-2016 10:41 AM
Normally that's true. The default settings of the app builder remove the block diagrams.
But it is possible to have settings that leave all the FPs & BDs intact, in which case the VIs would be fully extractable from the .exe.
07-25-2016 10:53 AM
Mostly true. A small % of VIs have characteristics that allow their BDs to be pried open without ever discovering the password.
07-26-2016 11:42 AM - edited 07-26-2016 11:47 AM
I disagree with this statement. I'd say every VI from when password protection was conceived to the newest version can be opened without the password in about 5 different ways, some more successful than others. Even NI R&D has said something to the effect that the protection you get from password protecting a VI is about the level of protection you get from tissue paper.
You can use VI Server calls to brute force it, perform reverse MD5 hashing on 2011 and older (salt was added to 2012), you can hack LabVIEW.exe to not ask for the password, you can use the This VI reference (or brute force what this refnum is), or you can replace the password and hashes in the VI with a new one.
The source code is in the VI and it is unencrypted, for various reasons. This means getting access to it is very possible. The recommended method of properly protecting your IP if you are that conserned about it, is to remove the block diagram from the VI.
http://digital.ni.com/public.nsf/allkb/831F38C46BCBDADE8625793A0054BB19
A consern I have that is related to this, is the fact that a large majority of the tools network packages, and NI add on tools, all rely on this VI password linked to a passworded library to license the code. With the right tools it probably doesn't take much to just remove all licensing restrictions from all libraries.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord