Both of them are highly unpractical and costly! Get over it and accept that password protection of diagrams is only to keep out the nosy. If you do need to protect your IP don't distribute the source at all! Bite the bullet and remove at least the diagram. Yes it's inconvenient as such VIs can only be loaded into the LabVIEW version in which it was created and also only on that platform but anything else means LabVIEW has to be able to get at the diagram somehow without knowing the password or worse yet store the password in the VI somehow too and that also means that anybody with enough determination will be able to circumvent any kind of protection the LabVIEW developers can come up with to prevent others than LabVIEW itself to get at that diagram.
I think the best long term protection in that respect is actually the semi annual release cycle of LabVIEW as it obsoletes any of the more promising hacking solutions each time. I never said it was. I was simply pointing out that NI wouldn't "cry" over a password protection hack and that since the licensing has been compromised; they would be more concerned about that-if at all.
Does anybody remember an old DOS program from around ? If memory serves me correctly it was called Burp-Cotch-Spit!
Googling that came up with some interesting results I never used it, but definitely played around with similar tools. I messed around with all sorts of Apogee and 3D Realms games I'm not a cryptology at all, zero experience what so ever, but I've often mentioned how not secure the password protection method is despite a few NI employees telling me otherwise.
But I'm starting to understand now why it is done the way it is. I thought that the whole VI should be encrypted, making it impossible to find the MD5 of the password in the file. I now know why NI can't do that. Which would still be pretty secure for passwords 10 characters or greater which aren't susceptible to dictionary attacks. It's a violation of the license agreement indeed, though I doubt a hacker feels much bothered by that.
The other issue is that you need to do disassemble and that is not trivial. Even a very good disassembler takes a few hours to get a raw disassembly for such a huge executable. And then you can sift through million lines of assembly code to find the places where the MD5 hash is checked. And looking at assembly for even a k DLL is already a rather boring job.
The fact that every half year a new executable is released makes the task even more hopeless. So while I'm sure there exist hackers who have hacked one or two versions of LabVIEW to that extend they really won't keep on doing that over the years as the gain of this is minimal. There is very little you can really see from most password protected VIs. Bragging rights don't apply because if someone does that, he might get a cease and desist letter or even worse, signed by the legal department of NI.
I have at some point looked at the possibility to simply modify the VI and that seemed just as hopeless. Especially with VI libraries involved, which contain also a password whose hash is even out in the clear in the library XML code. And those passwords even seem to be interwoven with each other. As to the licensing. After all why should a hacker who doesn't respect intellectual property respect someones privacy? You say that because new executables are released every 6 months, that this would deter the hackers.
But then you mention the license generating hacks. I also don't know what techniques the hackers use to create license generators, but from your explanation it sounds like alot of work went into figuring out how to modify this one version of LabVIEW to open VIs with passwords. I haven't seen it, but this post leads me to believe that. Even this thread makes me nervous. However not talking about it may give the false sense of security, thinking that LabVIEW is secure when protecting source code.
Your reasoning mixes again two rather unrelated things. For both you do need to to dig into disassembly if you don't want to go the brute force attack through GPU path, but they are not directly related to each other. I haven't looked at the details for some time, but from what I saw earlier the license generators you could find were always tied to very specific LabVIEW versions.
And they don't work for NI, as NI has of course the ability to work on the source code directly to circumvent such protection. This means, don't trust your super secret 5 million dollar idea to password secured VIs but also don't expect or require NI to provide such a possibility. It is technically simply not feasable to create a really secure protection without at the same time throwing away the advantage of not having to remove the diagram and making a VI only readable in the specific version and platform it was created in.
You can post now and register later. If you have an account, sign in now to post with your account. Paste as plain text instead. Only 75 emoji are allowed. Display as a link instead. Clear editor. Upload or insert images from URL.
By using this site, you agree to our Terms of Use. Followers 3. NI recommends that you have several megabytes of disk space available for this temporary directory. NET 4. Windows 8. Downloading the Software You can download the installer from here. This information is mostly irrelevant. Hit Next when you are done Next, you will be asked for your serial. You should have received your serial from Studica. The serial should look something like this: A12B Customize a Thing. Full Version Labview 8. Download All Files.
Select a Collection. Save to Collection. Tip Designer. Share this thing. Using Labview Vi Password Cracker crack, password, registration codes, key generators, serial numbers is illegal.
LabVIEW Crack Crack Free is here, this software is latest and enhanced graphical programming approach instead any type of code to make apps. Additionally, this program gives you user friendly environment to create applications.
0コメント