Slashdot Mirror

← Back to Stories (view on slashdot.org)

The 2006 Underhanded C Contest Begins

Posted by ryuzaki0 on from the segmentation-fault-core-dumped dept.

Xcott Craver writes "The second annual Underhanded C Code Contest is live as of April 4th, and runs until July 4th. The object is to write malicious C code that looks perfectly readable and innocent under informal inspection of the source."

4 of 232 comments (clear)

  1. I'll submit the source code for... by IIDX · · Score: 0, Flamebait

    Windows!

    Oh darn, it's not written in C.

  2. In my experience by Billosaur · · Score: 0, Flamebait
    ...in this contest you must write code that is as readable, clear, innocent and straightforward as possible, and yet it must fail to perform at its apparent function. To be more specific, it should do something subtly evil.

    That sounds like most of the C code I've ever seen... or written, come to think of it...

    --
    GetOuttaMySpace - The Anti-Social Network
  3. Any C code is potentially malicious by jb_nizet · · Score: 0, Flamebait

    To me, as soon as the C code uses pointers, it is potentially malicious. That's one of the reason why so many people choose Java, C# or other pointer-free languages.

    1. Re:Any C code is potentially malicious by Arandir · · Score: 1, Flamebait

      Sorry, but you're an ass. You've been fed a diet of shit so long you think it tastes good. Pointers aren't a problem, improper use of them is. Surprise! Improper use of ANYTHING is a problem!

      Undisciplined use of pointers is going to cause bugs. But since undisciplined coding itself causes bugs, who the fsck cares? The solution isn't to ban pointers, but to start beating undisciplined coders over the head. I'm not saying you have to use pointers, but if you are avoiding them because of fear, it's time to learn how to use them properly.

      --
      A Government Is a Body of People, Usually Notably Ungoverned