Sparkette Posted February 6, 2019 Report Share Posted February 6, 2019 (edited) And do I really want to know? 1gn0rance1sbl1ss, after all. 😜 Edited February 6, 2019 by flarn2006 Quote Link to comment
Sparkette Posted February 7, 2019 Author Report Share Posted February 7, 2019 (edited) 15 hours ago, ShaunR said: It depends on the pr0j3ct. You know it be true. How about Pr0ject411? Edited February 7, 2019 by flarn2006 Quote Link to comment
David_L Posted February 10, 2019 Report Share Posted February 10, 2019 Man, I need context... Quote Link to comment
jacobson Posted February 10, 2019 Report Share Posted February 10, 2019 Just ask Bob L. 4 hours ago, David_L said: Man, I need context... It's Flarn, just assume he's talking about something that you're not supposed to touch. 1 Quote Link to comment
Sparkette Posted February 11, 2019 Author Report Share Posted February 11, 2019 Bob L? I think he prefers to go by RobertLewis. Quote Link to comment
Sparkette Posted February 11, 2019 Author Report Share Posted February 11, 2019 Well, not supposed to know according to NI. But of course it's my brain, not theirs. Just mytwocents. Also, there's a reason MD5 has fallen out of favor, you know. 😛 Quote Link to comment
shoneill Posted February 11, 2019 Report Share Posted February 11, 2019 Passwords I'll assume. Quote Link to comment
hooovahh Posted February 12, 2019 Report Share Posted February 12, 2019 Yeah I used to have a list of the passwords I had reversed but I can't find it at the moment. I think there was something about Looking Glass , Jack Black, Jabber Wocky, Axes Of Eval, FP Rocks, and a few others that were random characters and harder to remember. I (probably like you) wrote code to go over the most common word lists for words of 5 characters or more, and for 1-4 I just brute forced all combinations, then after that used a program to reverse MD5s using your GPU. It was slow, painful and each new version of LabVIEW added more and removed some. I bet with the advent of new graphics cards this process could be made easier. There is a method in LabVIEW to add known passwords to a cache, and then not prompt if they have been entered so I thought it would be a neat VI to just run which would make looking at all NI VIs easier rather than writing code to replace and remove the passwords thereby changing the VI which I don't like. Maybe we could make that VI, and then password protect it? Quote Link to comment
shoneill Posted February 12, 2019 Report Share Posted February 12, 2019 (edited) One VI to rule them all, one VI to find them, One VI to bring them all and in the darkness bind them. Edited February 12, 2019 by shoneill Quote Link to comment
ShaunR Posted February 12, 2019 Report Share Posted February 12, 2019 24 minutes ago, shoneill said: One VI to rule them all, one VI to find them, One VI to bring them all and in the darkness bind them. Uhuh. Quote Link to comment
hooovahh Posted February 12, 2019 Report Share Posted February 12, 2019 Yeah something like that. The password replacement code I think is still posted online in PHP. I wrote the G equivalent and posted the read-only parts online. It has some pretty useful thing like being able to read information about a VI without VI Server. At one point I was able to figure out what objects are on the front panel and block diagram by looking at the raw VI file. Of course doing this means you don't get the satisfaction of knowing what the password was. Quote Link to comment
Neil Pate Posted February 12, 2019 Report Share Posted February 12, 2019 Without fail I have always experienced deep disappointment upon finally looking at the code hidden away by NI's. VIs tend to fall into one of two categories: wow that is such messy code no wonder they keep it locked way! DLL call... blergh  Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.