Bug in challenge 16

[commjoen]

The obfuscated front-end function does sometimes give back a different value than the actual value used in the backend in challenge16.
We need to:

• make sure we get the right value from the obfuscated function (e.g. fix function generation/obfuscation/integration)
• create a test as part of the container building that verifies using the value in the generated secondkey.txt is indeed valid (not returning 401, but 200 instead)

Want to take this issue on? You will need to have understanding of Bash, node, mvn, and the overall architecture of the project.

[commjoen]

in 1.8.2 the spoil, secondkey.txt and the javascript seem aligned again on arcane, the nomral container release (see latest docker and ctf-party), but not on prod heroku . still having a test to ensure this is the case before proceeding would be great!