Problem 1752. Get me! v4 (Cody hacking challenge)

You opened the pandora box! This destroyed my hope on a cody anti-hacking framework... :'( This solutions means two things: 1 - Mathworks guys will have a hard-time shielding cody (if they dare to); 2 - Matlab is such a beautiful highly-customizable piece of software!

thanks, and I agree with both your points :) but please don't give up, this series has been fun!. In any way, my two cents, I believe if you avoid 'assert' (e.g. instead of 'assert(condition)' use something like 'if ~condition, 1/[1 1]; end') you should be able to lock down any evaluation code pretty safely (just need to avoid using functions that may be overloaded by the user routines, and be careful against 'evalin' attacks... hacking attempts would then need to target the Cody code instead of your evaluation code).

A collegue just told me about a DSP challenge on you tube. Level one its just too lame, so here is the link to the second level: https://www.youtube.com/watch?v=0lbgepTiIaU