The First Annual Underhanded C Contest 341
Xcott Craver writes "We have just announced a new annual contest, the Underhanded C Contest, to write clear, readable, innocent-looking C code that implements malicious behavior. The object is to hide evil functionality that survives visual inspection of the source. The prize is beer."
Comment removed (Score:5, Funny)
This will work (Score:4, Funny)
in other words... (Score:4, Funny)
Re:What are the legal ramifications of this? (Score:3, Funny)
Beer? Phui! (Score:2, Funny)
The prize is world domination!
Re:This will work (Score:5, Funny)
I think I might win (Score:4, Funny)
main()
{
printf("Hello World");
}
Seemingly harmless, right? Wrong. It's still in devlopment, but think about it. You should have to greet the world before you destroy it.
like this? (Score:5, Funny)
void main()
{
screensaver(); * function */
anyone that thinks there is * / needs */
}
585
Here you go (Score:5, Funny)
Just tuck it away in a commonly used header file, use touch to restore the last date/time of modification, and you're all set.
#define void int
Hours & hours of irritation & confusion!
T&K.
Re:What are the legal ramifications of this? (Score:5, Funny)
Re:SxE anyone??? (Score:3, Funny)
What if someone in the straight edge crowed wins?
They can give the beer to me.
Here's my entry: (Score:3, Funny)
root (hd0,0)
chainloader +1
Now where's my beer?
Diebold Hiring the winner! (Score:4, Funny)
Diebold needs new programmers. If you have what it takes to hide "winning" code in our election machines. Apply to Diebold Careers [diebold.com]
Re:Diebold (Score:3, Funny)
It's supposed to survive inspection, remember. giveElectionToTheRepublican() is underhanded, but it probably won't survive inspection.
Cheating? (Score:3, Funny)
Would the Windows source code count? (Score:2, Funny)
Subtlety (Score:5, Funny)
Some dude from Microsoft is gonna win... (Score:5, Funny)
He'll submit the source code to IE.
Re:like this? (Score:5, Funny)
here's my entry (Score:4, Funny)
how's this? (Score:5, Funny)
So The Hard Part Is To (Score:5, Funny)
Wow, nobody's going to win this one.
Re:in other words... (Score:3, Funny)
Re:If crashing is "malicious behavior" (Score:3, Funny)
Nope. Only the code that includes
#include <windows.h>
*ducks*
Re:how's this? (Score:2, Funny)
Obligatory simpsons paraphrase (Score:5, Funny)
Judge: 'That's bad.'
Programmer: 'But it's optimized for PowerPC!'
Judge: 'That's good!'
Programmer: 'PowerPC is also cursed.'
Judge: 'That's bad.'
Programmer: 'But you get your choice of operating systems!'
Judge: 'That's good!'
Programmer: 'The operating systems run on Intel.' *pause* 'That's bad.'
Judge: 'Can I go now?'
I think this is more appropriate (Score:3, Funny)
main() { printf("Goodbye World!\n"); }
Re:It's a bad idea (Score:4, Funny)
Source [york.ac.uk]
Re:Here you go (Score:2, Funny)
You see, I had to write some kind of simulation program that required a huge array of numbers. I wasn't sure whether to use "long int", to avoid overflow, or "short int", to avoid wasting memory. So I thought, "OK, I'll use a typedef, and so if I pick the wrong type, I can easily change it later."
But I was afraid that, out of habit, I would accidentally use "int" instead of my typedef. So I "temporarily" added "#define int ERROR" to my code.
Unfortunately, by the time I got around to compiling "int main()", I had completely forgotten about that #define, and couldn't figure out where the compile error was coming from.
Re:This will work (Score:2, Funny)