Smell as Sweet
Smell as Sweet
Wireshark is definately some kick-ass software. It helped me to get the answer within a few minutes.
How did you solve this challenge?
How did you solve this challenge?
-
- Posts: 4
- Joined: Sun Oct 17, 2010 3:30 pm
tcpflow to sort the packages, then foremost to extract the images.
Extracting the html was a bit more tricky:
to find out where to look and
to extract these lines.
Wireshark would have been easier though^^
Extracting the html was a bit more tricky:
Code: Select all
cat -v dump | grep -n html
Code: Select all
cat dump | head -n 81 | tail -n +8 > file.htm
Wireshark would have been easier though^^
at first i tried just dumping all the pngs (since the html was obviously a single packet so you knew where to start and stop) but the background image was corrupt. assuming it was important (silly me) i then started writing my throw away program
i wrote my own packet parser from scratch using wireshark as a guide (i didnt know how to import/export packets at the time so i reversed the protocols) and dumped each "file" worth of a packet. lucky for us it didnt do anything tricky like packets out of order or dropped/unsolicited packets though i still havent figured out the first 0x18 bytes but i assume its some kind of router packet protocol, since it only happened once i just ignored it.
i wrote my own packet parser from scratch using wireshark as a guide (i didnt know how to import/export packets at the time so i reversed the protocols) and dumped each "file" worth of a packet. lucky for us it didnt do anything tricky like packets out of order or dropped/unsolicited packets though i still havent figured out the first 0x18 bytes but i assume its some kind of router packet protocol, since it only happened once i just ignored it.
-
- Forum Admin
- Posts: 496
- Joined: Sat May 28, 2011 9:14 am
- Location: Germany
So you didn't need the background image at all? Huh.
I guess the easiest and the fastest way to solve this is simply to make one educated guess. Just open file_20080914 in a text editor, read the line "the answer, my friend, is" and from there on you need neither Wireshark nor the C program I wrote to extract the .png files...
By the way, can somebody who understands Javascript explain to me how the "encoding" of the solution actually works here? I thought at first that the images would be moving around on the screen, and in conjunction with the background would reveal the answer when you look at them in the right moment or something... but obviously that is not how it works?
I guess the easiest and the fastest way to solve this is simply to make one educated guess. Just open file_20080914 in a text editor, read the line "the answer, my friend, is" and from there on you need neither Wireshark nor the C program I wrote to extract the .png files...
By the way, can somebody who understands Javascript explain to me how the "encoding" of the solution actually works here? I thought at first that the images would be moving around on the screen, and in conjunction with the background would reveal the answer when you look at them in the right moment or something... but obviously that is not how it works?
- livinskull
- Posts: 22
- Joined: Fri Jun 26, 2009 12:01 pm
- Location: /dev/null
- Contact:
pngcheck - another possible tool
Wow, I was puzzled on how to extract the png's, but I managed to solve it after finding pngcheck from another challenge (and the funny thing is, I haven't solved that one yet ). Anyway, I haven't heard about wireshark - it definitely sounds promising.