Time to test your skills on a harder version of task$1.$ This time not only the labels are missing, but someone invented their own calling convention, which you will also have to reverse$-$engineer.

Your very own task$2$

You will get your very own task$2.$ To generate it$,$ run:

~cpen$212/$Public$/$lab$1/$task$2$gen

This will create a task$2$ in the current directory $($so you better have permissions there, or it will fail$).$

This also accepts one argument. This argument is a password, and task$2$ will either print PASSED or FAILED depending on whether you've provided the correct password.

Analysis

In this and the next task, you will use the skills you learned in Task $1$ to determine how task$2$ checks its input.

For this task, start by identifying all functions and the addresses like in Task $1.$ Then determine as much as you can about the calling convention being used by the program $($argument and return registers, caller$-$saved and callee$-$saved registers, etc$).$ Note that the calling convention being used is likely different from what we covered in class.

Finally, there are four checks that the program performs on the password it receives. If any of these fail, the program reports FAILED, and if all four pass, then the program reports PASSED. For each of those checks, determine the address of the toplevel function called to determine whether the individual check passes or fails.

As before, there is a task$2/$task$2.$c file you need to fill out with the corresponding questions in task$2/$task$2.$h$.$ Also as before, your code must compile, link, and execute on bare metal, and may not have any side effects. Be sure to test your code $$ for example by adaptng the check program from Task $1$ as you will receive no credit if the program doesn't compile, crashes, or returns incorrect results.