Author
Message
Wolf
Decorated
Joined: 26 Sep 2002 Posts: 292
Maybe we'll get another e-mail slap in the head from our 7331 h4x0rz again.
Krystyn, check your PMs. I'm coming to Chicago this weekend.
_________________You can lead a horticulture, but you can't make her think.
Posted: Wed Nov 10, 2004 11:16 am
krystyn
I Never Tire of My Own Voice
Joined: 26 Sep 2002 Posts: 3651 Location: Is not Chicago
Roger that, Wolf.
I would almost say that we've used up our e-mail h4xor connections. They have been more than generous, and I know I feel as though I've personally let caesar and the gang down by not being more timely with the solves.
What's tripping up my puzzle-challenged brain right now is that there isn't an obvious corollary to the Mu game, since we pretty much never had steg, except for that one gimme I put into Paintover in order to appease the steg-hungry masses (the file cabinet image). Later, I did insert text into a caesar image, but it was just stuck into the data all raw and stuff.
ETA: the only other thing that occurs to me is Morse code. Perhaps reading from top-to-bottom, left-to-right might yield some sort of message? My gut says it's nothing of the kind, but I thought I'd throw it out there.
Posted: Wed Nov 10, 2004 11:48 am
spriggan
Boot
Joined: 29 Oct 2004 Posts: 25 Location: Cambridge, MA
were there any kinds of hardcore cryptography (not steg) puzzles in the original game? i'm thinking the 128bit key.dat, the reference to JPEG compression as the encryption method, and that the image is called data.jpg are pretty big hints for somebody that knows more about this kind of stuff.
_________________--
kevin
Posted: Wed Nov 10, 2004 1:35 pm
GWing_02
Veteran
Joined: 18 Aug 2004 Posts: 144 Location: Seattle, WA
Ehsan wrote:
Then there will be far too many 0's for it to mean anything.
Oh yeah, forgot about that.
Quote:
I'm not even sure if they mean anything or are they JPEG artifacts? So far I haven't been able to find a single document that explains the JPEG file structure, which is weird because I remember seeing some a while back which had examples and proper explanation.. I think we need a hint on this one.
Basically JPEG compression is that only every few pixels are filled in-- the rest is interpolated. They wouldn't be image compression issues, but they may be artifacts relating to the data they hid.
Posted: Wed Nov 10, 2004 11:31 pm
GWing_02
Veteran
Joined: 18 Aug 2004 Posts: 144 Location: Seattle, WA
Okay, so I'm doing a little more searching on JPEG compression as an encryption tool. Here's some results...
This site (link) wrote:
Pyramidal tiling typically uses the process of "internal tiling," where each tile is encoded as part of the same JPEG data stream. Tiles may optionally use the process of "external tiling," where each tile is a separately encoded JPEG data stream. External tiling may allow quicker access of image data, easier application of image encryption, and enhanced compatibility with certain JPEG decoders
There doesn't appear to be any tiling here, though, does there?
And that's all that I could find. A program here or there that don't fit at all with what we have on our hands, and that's it.
Hint time...
Posted: Thu Nov 11, 2004 2:36 pm
spriggan
Boot
Joined: 29 Oct 2004 Posts: 25 Location: Cambridge, MA
from what i understand of steg (what i have learned in the past few days), using a plain black image to hide another file is a dead giveaway; you generally want to use images with a lot of detail. so i'm guessing that the fact that the image is all black a bit of obvious garbage, that we're supposed to get the hint that this is a stegged image.
i base64'd key.dat to get a decent looking key (is that the right thing to do?), then used jpseek with that key to try to desteg the image, but got garbage. however, i am using the linux version, so maybe the windows version is different. anybody want to try? here is the base64'd key.dat:
dBwNEhIEFRwNFxsaFQ8HCw==
if this is a shoutout to the paintover puzzle, maybe we should try using the same destegging method that solved that one.
_________________--
kevin
Posted: Thu Nov 11, 2004 8:41 pm
GWing_02
Veteran
Joined: 18 Aug 2004 Posts: 144 Location: Seattle, WA
I don't think base-64'ing the key is a good idea. you now have a 192-bit key instead of the sensical 128-bit key we had before. Just because the key wasn't all characters doesn't mean it wasn't valid. The bit data just didn't happen to be defined as a readable character in ASCII.
Posted: Thu Nov 11, 2004 9:13 pm
spriggan
Boot
Joined: 29 Oct 2004 Posts: 25 Location: Cambridge, MA
GWing_02 wrote:
I don't think base-64'ing the key is a good idea. you now have a 192-bit key instead of the sensical 128-bit key we had before. Just because the key wasn't all characters doesn't mean it wasn't valid. The bit data just didn't happen to be defined as a readable character in ASCII.
when i was trying the straight decryption methods (not destegging) i was using the normal key.dat file as a 128 bit key. when i switched to destegging, i went to base64 because the jpseek program wants the user to type in a password. (i did try pasting in the key.dat data as well but who knows if it was parsed properly.) i'm not sure which is more appropriate for jpseek/hide, 128 bit key or text password of any length. i am basically trying anything i can think of. but i agree that the 128 bit length of key.dat seems important.
_________________--
kevin
Posted: Thu Nov 11, 2004 9:19 pm
AnthraX101
Entrenched
Joined: 18 Mar 2003 Posts: 797
Spoiler (Rollover to View):
The ^ was the tipoff. It's the XOR feedback cipher again. Take every letter and XOR it with the value of the previous letter in key.dat.
Spoiler (Rollover to View):
theweatherisfine
Spoiler (Rollover to View):
Run it through JPSeek:
Urer jvyy V fgnaq gvyy Pnrfne cnff nybat,
Naq nf n fhvgbe jvyy V tvir uvz guvf.
Zl urneg ynzragf gung iveghr pnaabg yvir
Bhg bs gur grrgu bs rzhyngvba.
Spoiler (Rollover to View):
And next ROT-13 it:
Here will I stand till Caesar pass along,
And as a suitor will I give him this.
My heart laments that virtue cannot live
Out of the teeth of emulation
AnthraX101
_________________VGhlcmUgaXMgbm8gc3Bvb24u
ll----ll--ll--ll----l---ll---llll---ll--l--ll---llll-ll-l-ll-llll--l-.
Posted: Thu Nov 11, 2004 9:38 pm
spriggan
Boot
Joined: 29 Oct 2004 Posts: 25 Location: Cambridge, MA
AnthraX101 wrote:
Spoiler (Rollover to View):
The ^ was the tipoff. It's the XOR feedback cipher again. Take every letter and XOR it with the value of the previous letter in key.dat.
Spoiler (Rollover to View):
you mean the ^ in the title of the inner frame pages? nice. i never noticed that before now.
_________________--
kevin
Posted: Thu Nov 11, 2004 9:48 pm
krystyn
I Never Tire of My Own Voice
Joined: 26 Sep 2002 Posts: 3651 Location: Is not Chicago
oh nooooooooooooooooooooooooooo!
Posted: Thu Nov 11, 2004 11:03 pm
GWing_02
Veteran
Joined: 18 Aug 2004 Posts: 144 Location: Seattle, WA
AGH. WHY didn't I make that connection? I was just DOING XORs in C++ today (assignment due in 4 months... I'm a little ahead). WHY am I always 4 steps behind in every puzzle in this game!?
Posted: Thu Nov 11, 2004 11:17 pm
Display posts from previous: All Posts 1 Day 1 Week 2 Weeks 1 Month 3 Months 6 Months 1 Year Sort by: Post Time Post Subject Author Ascending Descending