07-17-2008 02:56 PM
07-17-2008 04:24 PM - edited 07-17-2008 04:25 PM
I have opened up one of my passworded vi's in the past with a brute force attack in LabVIEW 6i.
I used the following code by Michael Aivaliotis as a starting point. Regards, -SS
07-17-2008 04:28 PM
Well I can't answer your question, but I would like to note that I think this is a funny discussion.
Hope you can get access to those VI's 🙂
07-17-2008 04:33 PM
That code was exactly what I was referring to when I suggested the poster do a search. I did search, and found that code in about 1 minute, hence suggesting the poster do the same.
@ShotSimon wrote:
I have opened up one of my passworded vi's in the past with a brute force attack in LabVIEW 6i.
I used the following code by Michael Aivaliotis as a starting point. Regards, -SS
07-17-2008 04:44 PM
07-17-2008 05:37 PM - edited 07-17-2008 05:37 PM
There are simple techniques available to deal with the situation if the code is well structured and is basically sound. If you can find the appropraite sub-VI that performs the routine you want to tweak then re-write his VI matching his icon connector and save your non-password protected version over top of his.
If the top level VI is the issue and all of the logic is in it.... well maybe keeping his code is not worth the effort.
The good news is LV's password mechanism is good enough to frustrate most hackers.

But seriously, you usually don't want to get into every VI if the app is basically working so just re-write what needs changed. I have been involved in these situations before being on both ends of the game.
Ben
07-18-2008 01:42 AM
07-20-2008 07:00 AM
07-20-2008 08:15 AM
07-20-2008 08:54 AM - edited 07-20-2008 08:56 AM