topic Re: A call for obfuscated LabVIEW code in BreakPoint

A call for obfuscated LabVIEW code

altenbach — Sat, 26 Mar 2005 17:35:06 GMT

Discussions have come up in the past regarding the question if LabVIEW is a real programming language.

Some of the central points are discussed in detail in this LabVIEW Zone article by Jeff Kodosky. A more recent development was the addition of LabVIEW as a programming language to the software map at sourceforge.net.

One glaring omission so far has been the complete absence of any official obfuscated code contest such this one for C. (One might argue that some of the posted LabVIEW code here would qualify without any changes, but I am sure some of us could do even better! :))

To help round out the picture and add another milestone to the worldwide recognition of LabVIEW, I propose the

***** First annual obfuscated LabVIEW code contest *****

Since this is all still in its infancy, we would need to agree on some rules and guidelines. (Everyone can take an existing LabVIEW program, select everything on the diagram, followed by a "align vertically" and "align horizontally". This is boring.)

We are looking for amazing and surprising code filled with originality and creativity.

I am not entirely sure about the best way to do all this, so feel free to discuss the format. One possibility would be for everybody to post code entries here until a certain deadline, then we can nominate the top entries for a vote by poll.

Re: A call for obfuscated LabVIEW code

Ben — Sat, 26 Mar 2005 18:19:52 GMT

So to evaluate submisions we would have to be able measure degrees of obfuscation!

How do measure obfuscation?

What is obfuscation in a LV context?

If I entertatin the notation that obfuse (is that a word?) code is what I am not supposed to write then this would be bad code. But it still has to work?

Could we use the VI Analyzer backwards? Try to get most number of test failures and still work?

Should we rule out scripting? A VI that wrote and ran a VI that said "Hello World" would be pretty challenging to decypher.

Ben

Re: A call for obfuscated LabVIEW code

Ray.R — Sun, 27 Mar 2005 15:32:36 GMT

Guys,

Looks like it is a word..

DEfinitions:

1. To make so confused or opaque as to be difficult to perceive or understand: “A great effort was made... to obscure or obfuscate the truth” (Robert Conquest).
2. To render indistinct or dim; darken: The fog obfuscated the shore.

I am copying a paragraph from this site..

"Obfuscation works to transform programs in such a way as to not affect what the program does, while at the same time impeding reverse engineering efforts. In a nutshell, obfuscating transforms have a goal of destroying relationships that exist between the compiled and source-code versions of the code. Although initially the idea of actually making program code harder to understand seemed counterintuitive, it is now seen as a valuable component in computer security."

Obfuscated LV code...

Interesting idea.. It seems that to "REGULAR" SW people, LV is obfuscated enough 😉

But making a cryptic Hello World program could be somewhat very interesting... I LIKE IT!! 😄

We could do this as a fun-thing-to-do.. No rules.. Just really complicated-looking code that brings a popup with a message: "Hello World" for instance..

😄

Re: A call for obfuscated LabVIEW code

altenbach — Sun, 27 Mar 2005 18:35:51 GMT

Yes, I was thinking mostly about the definition labeled Recreational obfuscation on Wikipedia. 🙂

"Hello world!" is nothing more than a complex constant of [6.072132627989E-154 +1.512540973677E+113 i], see attached (LabVIEW 7.0, use execution highlighting!). 😉

Re: A call for obfuscated LabVIEW code

Enrique — Sun, 27 Mar 2005 20:08:13 GMT

Well, not with the intention of critisize, but I really don't like that way of obfuscating (hiding code behind other code, or a drawing, etc.). And, actually, your code was obfuscated enough the way it is!!

I'll like, or let me say, propose, that a rule for the LabVIEW obfuscation challenge to discourage that type of obfuscation.

I remember a while ago that there were several "Hello World!" obfuscated LabVIEW code because I posted a link about the "Evolution of a Programmer". I know have them somewhere... I'll look around.

Re: A call for obfuscated LabVIEW code

altenbach — Sun, 27 Mar 2005 20:33:25 GMT

No, you're absolutely right. "Stacking" of code elements should not be allowed. (Either by placing structure over code or resizing structures to be smaller than the code they contain, etc.).

I was trying to make a point that we need some rules. We also should not allow images of fake code on the diagram. 😉

(All these tricks should only be allowed on April 1.) 🙂

Re: A call for obfuscated LabVIEW code

altenbach — Sun, 27 Mar 2005 22:05:37 GMT

OK, here's my legitimate "Hello World!" Program.

It is probably possible with a little more effort to simplfy the code a bit ... but hey, if it ain't broke, don't fix it. 🙂

Message Edited by altenbach on 03-27-2005 02:06 PM

Re: A call for obfuscated LabVIEW code

tst — Sun, 27 Mar 2005 23:20:19 GMT

I must admit to a bit of cheating - I didn't write most of the code.
But hey, it's late here. I'm not in a creative mood at the moment.

Re: A call for obfuscated LabVIEW code

chilly_charly — Mon, 28 Mar 2005 11:09:00 GMT

And here is my contribution...

CC

Re: A call for obfuscated LabVIEW code

chilly_charly — Mon, 28 Mar 2005 16:46:01 GMT

From my pond deepest muddy hole, where I recover slowly from tst last chickenhearted assault, I have decided to be more carefull when trying to communicate all my friendship to others. And this is what emerged from my poor damaged brain : the ultimate translator.

I believe that JLV, JPD and tbob will enjoy that one.

Of course, it works with "Bonjour monde".

But there is much more... Just type some french words as input and see what happens.

I had a good laughter with "bonjour JLV", "bonjour tst" and "bonjour LabVIEW"

Come back with your own findings !

If I get enough stars, I will give you the password...

Enjoy

CC

Re: A call for obfuscated LabVIEW code

Ray.R — Mon, 28 Mar 2005 17:05:52 GMT

I will have to try this tonite..

😄

Re: A call for obfuscated LabVIEW code

altenbach — Mon, 28 Mar 2005 17:37:24 GMT

"URL Get HTTP document.vi" was not found. Is this from some toolkit?

Re: A call for obfuscated LabVIEW code

JeanPierre — Mon, 28 Mar 2005 18:43:53 GMT

I am especially proud of this devilishly simple one...

Re: A call for obfuscated LabVIEW code

altenbach — Mon, 28 Mar 2005 19:09:13 GMT

I like that one! 🙂

Re: A call for obfuscated LabVIEW code

Ben — Mon, 28 Mar 2005 22:26:10 GMT

I agree!

Now for those who have NOT posted yet, I will award bonus stars for whoever can explain why JP's code works?

JP and Altenbach you are allowed to give hints if you would like.

Ben

Re: A call for obfuscated LabVIEW code

altenbach — Mon, 28 Mar 2005 22:46:33 GMT

Hint: I challenge JP to adapt his VI so it works under LabVIEW 4.1. 😉

Re: A call for obfuscated LabVIEW code

chilly_charly — Tue, 29 Mar 2005 01:29:16 GMT

@altenbach wrote:
"URL Get HTTP document.vi" was not found. Is this from some toolkit?

Sorry ! I realise that this vi (and other subs) is part of the Internet toolkit. I'll try to post a working version later...

CC

Re: A call for obfuscated LabVIEW code

chilly_charly — Tue, 29 Mar 2005 02:40:40 GMT

@Jean-Pierre Drolet wrote:
I am especially proud of this devilishly simple one...

Excellent !

CC

Re: A call for obfuscated LabVIEW code

altenbach — Tue, 29 Mar 2005 03:05:36 GMT

Great!

Message Edited by altenbach on 03-28-2005 07:12 PM

Re: A call for obfuscated LabVIEW code

Enrique — Tue, 29 Mar 2005 03:38:40 GMT

Absolutely nothing obfuscated about this one. It is only fun to watch it with Highlight on.