4 ms·
I'm kinda annoyed that the judge completely misread my entry. I had it so that data was leaked out of a function that could not possibly leak data, via a malloc
by kayamon 11y ago
I'm kinda annoyed that the judge completely misread my entry. I had it so that data was leaked out of a function that could not possibly leak data, via a malloc side-channel attack (ala HeartBleed).
Instead it got judged as being a 'simple buffer overflow'.
Grrr.
- nitrogen 11y agoI'd call that a win. Even the judge was fooled.
- kayamon 11y agoI'll post up my complete entry in case anyone's interested to look through it: http://www.codersnotes.com/files/piupiu.zip http://www.codersnotes.com/files/piupiu.zip See surveil.txt for notes first. Someone below asked what makes this different from the Obfuscated C contest. In this contest, the idea is to make code that looks very clean and innocent. Entries that hide their behavior in weird ugly macros or just general C complexity are not really in the spirit of the contest. I tried to make my entry very clean so that there is obviously no malicious code anywhere in it.
- rcthompson 11y agoDo the judges get to read your explanation before deciding the results, or do they just have to decide based on the code?
- kayamon 11y agoI sent an explanation with it, no idea if anyone read it or not.
- umanwizard 11y agoEdited to remove spoiler.