Is there anyway to remove the password in vi?

[Wiebe@CARYA]

Actually, if a vi in the exe has a front panel (if it has locals, property nodes, or if this option is tagged in the builder) you can also get the front panel.


Also, you can get the hierarchy and connector panes. And you can run the vi's seperatelly, so you can analyse the individual vi's as little black boxes.


Regards,


Wiebe.




"Dennis Knutson" <x@no.email> wrote in message news:1151503811971-384681@exchange.ni.com...
The source code does not exist at all because the block diagrams have been removed. All that you can do is determine the names of the individual VIs that are part of the exe.

[Conseils]

I must be one of the few Dennis.....

This thread has links that could be of interest, including some details of none other than my own test of VI security (based on work by M.Aivaliotis {I seem to recall}).
http://forums.ni.com/ni/board/message?board.id=170&message.id=161139

The following may illuminate a little.
http://digital.ni.com/public.nsf/websearch/BC99793C48857A41862565BC006F472C?OpenDocument

And the following may also be of interest for background, there are some excellent comments by Enrique and Rolf with fascinating comments by Greg McKaskle2
http://forums.ni.com/ni/board/message?board.id=170&message.id=76302&requireLogin=False

Don't forget you can rate those answers yourself.... even if they have already got some shiny Stars. Stars are for giving.

[Ray.R]

Good phrase:" Don't forget you can rate those answers yourself.... even if they have already got some shiny Stars. Stars are for giving."

Is this your new signature?

Some stars went your way 😉

[Henrik_Volkers]

So as a conclusion:

It is security by obscurity!

---

Greg McKaskle2 wrote:

[..]

The diagram isn't encrypted, partly because of the
time penalties involved, and partly because we originally thought it
would be important for us to be able to unlock VIs if employees left an
organization, etc.

[...]

In short, it is sound and is quite hard to break.

Greg McKaskle

---

Please correct me:

The protection of the diagram is 'the black magic' how it is stored in the vi.

Obviously it's not as clear as a SPICE netlist, however there seems to be a strict (reversible) algorithm behind it. As Wiebe (and others) stated even your  PC-LV can read it, but just don't let YOU read it.    

It's secure because since now nowbody was willing to do the work of disassembling or succeed in other ways to find out how the diagram is stored.

[shoneill]

I think Henrik might be right.

Sounds to me hat if you could work out the contents of the VI file in binary, then it would be possible to read it, remove the password, set whatever flags to being not password protected and then re-write the file to disk.

I reckon that if the file format were known, it'd be relatively easy to do if the block diagram really isn't actually encrypted.....

Shane.

[K C]

You can use brute force and try all possible combinations in a string of x length in a LV program. Will keep you busy for a decade or more.

If you try to ‘break in’ into a VI from someone else…………. .

If you forgot your password but know what it could be you can make a Labview program to check all possibilities with and without capitals and whatever you use for passwords.

I did this once for a Word document, which I protected and wanted to use after years. I used a few passwords during that time and I was not sure if and how I used capitals.

I wrote all passwords I knew in a text file and the program just tried all these passwords with and without all capital possibilities. I was easier (and more fun) to do it with a LV program then trying to type all passwords.

Today I use only two password and never forget them, It is not good I know but it is easier for me on my age

[shoneill]

KC,

the whole point is that a decryption isn't neccessary since the block diagram is't encrypted.  It's just that the only front-end which can show you the block diagram won't show it unless you type in the password.

Since the password isn't actually needed to access the block diagram code, simply data surgery might suffice.....  If you tell LV that the VI doesn't have a password (And regenerate the checksum I presume) then all is OK.  No brute force, just a small nip and tuck.

Shane.

[Henrik_Volkers]

---

@shoneill wrote:
KC,

the whole point is that a decryption isn't neccessary since the block diagram is't encrypted.  It's just that the only front-end which can show you the block diagram won't show it unless you type in the password.

Since the password isn't actually needed to access the block diagram code, simply data surgery might suffice.....  If you tell LV that the VI doesn't have a password (And regenerate the checksum I presume) then all is OK.  No brute force, just a small nip and tuck.

Shane.

---

Changes might be simpler, if you disasemble and analyse the (labview.exe) code. You even don't have to regenerate the checksum, you 'just' have to change one or two conditional jumps in the labview.exe to skip the password and checksum, or just invert the result, so your 'cracked' version will only open protected diagrams.

[becktho]

Why not start a new thread: How to hack LV :D:D:D.

By the way Henrik - nice signature, but you should specify the sign. I don't know if it's easy to use a negative phone :D:D.

[Henrik_Volkers]

beckto,

I have no intention to hack LabVIEW, I prefer to hack with LabVIEW

When it comes to security in IT people often get blended by the shiny complexness of the systems, but it's all just 010101...

Sig: Lefthand or Righthand system ?? Or : Did you ever had a company mobil?