0 votes
In question 11 you ask us to submit the exact input that causes the bug to happen, but apparently, if you append anything to the string "syssec@upb", such as "syssec@upbabcd", this still triggers the bug.

In my case afl++ found the input crashing the binary to be "syssec@upbss" which, when tested with the binary, leads to the output:

Tessa rocks :)

Segmentation fault (core dumped)

Of course, I copied what afl++ produced and didn't think much of it. I don't think it's fair for this not to count, since the binary still crashes.
by
edit history

1 Answer

0 votes
Best answer
Hi,

Thanks for the heads up, we will correct that!

FYI: Your answers are automatically graded once the time is up. We manually check and regrade your submissions to account for such cases. In the meantime, correct answers such as this can be flagged as incorrect. This is to be expected, as Panda's autograding is not flexible enough in some cases.

Best,

Niklas
by (2.0k points)
edit history