Initially, it seems like for Forensics 200 Challenge #2 was the same as Challenge #1 when i saw the image below.
So immediately, i whipped out pngcheck again and i got back the following result.
I've tried "hughes connie" as the key but sadly it's not.
Then i relooked at the options for pngcheck and found out that it will stop checking after it found the first error.
Options:
-7 print contents of tEXt chunks, escape chars >=128 (for 7-bit terminals)
-c colorize output (for ANSI terminals)
-f force continuation even after major errors
-p print contents of PLTE, tRNS, hIST, sPLT and PPLT (can be used with -q)
-q test quietly (output only errors)
-s search for PNGs within another file
-t print contents of tEXt chunks (can be used with -q)
-v test verbosely (print most chunk data)
-vv test very verbosely (decode & print line filters)
-w suppress windowBits test (more-stringent compression check)
-x search for PNGs within another file and extract them when found
So in order for it to continue, i needed to add in the "-f" option.
But once i added that, it seems that the entire file is full of CRC errors.
Hmmm...could it be like what the words on the image implied? "One of these things xs not like the other" Thus, one of the tEXt chunks is not having CRC error.
Okay, let me pipe out the output into a text file.
Since there could be only be 1 without CRC error, i load up the output file and after looking at it for a minute. I realised there are too many entries to manually find the one that i'm looking for.
Then i realised that all i have to do is to do a quick search in Notepad++ for "}\r\ncomment:\r\n key{" as this is the sequence for checking the entry with no error. :D
Finally, we could find this.
There you go, the key to this particular challenge is "johnnie tigger"
Cheers,
Jacob Soo
No comments:
Post a Comment