So I was able to get the password by running the program in the shell and copying & pasting the second log - I'm assuming this was to help for debugging purposes and this isn't a valid way to crack this problem. |
==> |
How do you crack the md5 hash though, it's one-way. I found this 32-bit number in the code: 73eeac3fa1a0ce48f381ca1e6d71f077 - perhaps the unhashed version is the password, but that's impossible to figure out unless the solution is to patch the binary on the hash equality condition. |
==> |