forgot block diagram password

[vamsi v]

Hi

      I've forgotten my block diagram password. How can I restore it?

Thanx

vamsi

[Mathan]

see here

[jcarmody]

1) Rewrite the VI

2) Give it a new password. 

[Ben]

---

jcarmody wrote:

1) Rewrite the VI

2) Give it a new password. 

---

I'd suggest

1) Rewrite the VI

2) Write down new password

3) Set new password

I have read-up on people atempting to crack passwords of VI's and the best I have read about was IF the password was known, it could be found in the code. I have never read of anyone getting close without a hint.

Ben

[pallen]

Unfortunately, there's no easy way to do this. 

You might want to have a look here:  http://www.aivaliotis.com/archives/lv/vi_password_cracking.shtml

There was some partial code written awhile ago that might still be there.  I just tested the version I have on a VI with a password of "ab".  It took the unmodified code a couple of minutes to crack it.  I'm not sure though if it's even possible to crack even a medium security password. 

Good luck.

[Coq_Rouge]

Have you contacted your local NI office. They might help you. At least they could before. But they may have changed this policy. In any cases you have to in some way prove that you are the "owner" of the code. 

Anyway give them a call that is (almost) free

[Thoric]

In more recent releases of LabVIEW, the Set Lock State method has a mandatory 100ms pause for incorrect passwords. This means brute force password attacks can take a very very long time indeed if you're indexing through millions of automatically generated passwords from a large ASCII char table.

I know that in LV 7.1, this pause isn't enforced, but in 8.6 it is.

[rolfk]

---

t06afre wrote:

Have you contacted your local NI office. They might help you. At least they could before. But they may have changed this policy. In any cases you have to in some way prove that you are the "owner" of the code. 

Anyway give them a call that is (almost) free

---

No! As far as I know, NI stopped with that many years ago. The reasons are probably manyfold not the least would be the support effort for this, another one about the necessary verification that the person wanting to have the code unlocked is really entitled to see that code. The last but not least is probably that they do not even want to maintain a possibility to unlock password protected VIs.

So in such cases it is simply bad luck and the recommendation is to rewrite the VI again and be more careful about password protection. The nice thing is that rewriting a VI has for me in the past (not because of lost password but because of VI or HD corruption ) always resulted in cleaner, better maintainable and sometimes also much more performing code.

Rolf Kalbermatter

Message Edited by rolfk on 04-20-2009 11:11 PM

[MattBradley]

_____________________________________________________________________________________________________________________________________________________________________________________

The nice thing is that rewriting a VI has for me in the past (not because of lost password but because of VI or HD corruption ) always resulted in cleaner, better maintainable and sometimes also much more performing code.

_____________________________________________________________________________________________________________________________________________________________________________________

What a great idea!  I just deleted all of my VI's so I can rewrite them better!  Don't know why I never thought of that.

🙂