unforum

[JMAN 03]

Throughout the huge volume of embedded text that has been discovered, we've seen the "survive, evade,...., escape" phrase many times. What's interesting though is that they keep changing the exact choice of words used.

I've seen "Survive, evade, resist, escape" "survive, evade, reveal, escape" and even one "seek evade reveal resist"

The Operator is basically taking the original military phrase, "survive, evade, resist, escape" and butchering it over and over, inserting totally new words like "reveal" and "seek." This has gotten me thinking...

"Seek" is obviously a reference to the jpseek program, especially since it is usually associated in the text with "Hide and Seek," which is an even stronger reference to the JPHS program (not to mention The Operator's favorite game). So anywhere we see the word "seek" we should be looking for clues about a jpseek password.

Seeing the word "seek" thrown into the "survive, evade, reveal, escape...." bulljazz tells me that this phrase, in some form, might have something to do with the password we're looking for. So far, I personally haven't found a combination that works, but then again, I'm not very good at this stuff yet.

Does anyone have any thoughts on this?

[voipme]

[Zaphran]

I think someone on this forum http://anihina.com/forums/showthread.php?t=6385 has found the message in the pic we've all been stuck on and maybe some others..this could be a trout.. the stuff they found are as follows:

BEE_LOGO
Instead of /carrying them with /
her, she scratched /the ruby and /each of the /
greater blocks with /her knife, marking /
of her Queen's /domain./

- bee2_margaretphoto
To mend the queen's cuts the Window /took her sharp knife and /
peeled skin from the /bodies of her subjects, while the Queen's /
new eyes and ears she cut from those who had been /

- BEEBACKG
And when this /was so, the /Widow worked /
on, dry as sticks /and patient /as rust, driven /

- BUT_FUN
She cut her a /new mouth and /fed her /
with fireflies /and cakes of /
sand, /and /at /last /the /
Queen's /heart /began /to beat./

- BUT_HOME
the Widow came/ with three /
a staff /made of bone, and /a sharp /knife./

- BUT_ABOUT
At last /she had /come to /
the body of /her lady. The /
and still /and cold./

- BUT_HONEY
the /Widow /drew /
her /knife /and /slew /
the /Manticore /and /
the /way /was /open.

- BUT_THEHI
She walked /through the empty /
corridors of the /Keep searching /for her Queen, past /
the bodies of her /servants and subjects /
that lay /dead or enchanted./

- CUTEBEE
Long and /long she walked until /she came to the /
wall was low and/ broken, and/ the Widow passed/
through /like the /bleak wind./

- chloe.jpg
stone, this time a sapphire /no bigger than a winged /
ant, glinting on/ the cobbles of the courtyard /
before the walls of the Inner Keep./

- dana.jpg
The Queen was gone, /and in her place lay only /an empty crown. By great enchantment/she had been mazed /
and beholding herself, was within them./ And there, with the crown still upon/ her brow, lay the Queen./

- danadress.jpg
Within, she noticed what/ looked like a chip of precious /
ruby from the Queen's crown, no bigger than a fly. Around /
across a wide plain of lodestone./

- danapicnic.jpg
Queen returns to rule, and further /let it be known that retribution on any /who hinder the return of the Queen will /be swift and terrible./
At the feel of the Queen's pulse beneath /her bony fingers, the Widow next /took thought to proclaim through /all the Kingdom and into /

- margaret.jpg
When her Queen/

- farnsworth-window.jpg
The Widow said, "I am /the servant of your /
Queen, and I have walked up out of Hell to prepare this /
keep for her return. Let me pass." But the Manticore did /

- bee_garden.jpg
At the games of the Inner Keep all the guards were dead /
but one, who when the palace was blaster by /
enchantment had not died, but had been witched /

- CUTEBEE2.gif
small that /even the Widow, /
sharp /eyes, could /hardly see Him, /
and when she looked/ his way, he hid./

- figure.jpg
castle, slaying many guards and reaching through the Inner /
Keep to lay low / the Queen that held dominion there /

- langshivel.gif
The Sleeping /Princess lay /in the deepest /
glass where the /Widow could not hear /
her breathing./

- smoker.jpg
what I dreamed./
Everything died, and I /

[Shad0]

[Zaphran]

ah damn. thanks for the trouting.. *goes back into corner*

[Shad0]

Re: Trout

[JMAN 03]

jpseek

[tsioc]

maybe off topic, but where can I get a win32 binary of stegbreak or similar software?

I can spare my cpu cycles, running an Athlon XP 2500

I would love to help out in any way i can. Even if it's just running a brute force attack without using a dictionary, I would do it... I;m very new to this entire thing and have nothing else going on.

[peeveen1]

Am I right in saying that the passphrase check is case-sensitive? Hells bells ...

[Roc]

yes, passphrases are case, whitespace, and punctuation sensitive.
a windows binary for stegdetect/break/etc can be found at www.outguess.org

'dictionary attack' simply means you're testing a file of potential passphrases in bulk. It is not restricted to using an actual dictionary of single words. Personally, I was compiling my own dictionary of multiword phrases from the ARG-fiction text; with various punctuation, and modifying the rules.ini in stegbreak to test trivial variations (all caps, all lower, proper case, no whitespace, no punctuation, append/prepend 7 8 14 24 49 343, etc)

The stumbling block was when we discovered that, as is, stegbreak is incapable of accurately testing a passprhase of more than 16 characters.
This means that any potential passphrase greater than 16 characters must be tried by hand. With the outguess distro, that would be through manually running either jpseek or jphswin. Do that for a few dozen guesses, and you'll give up on trying to guess by hand pretty quick.

We need to find a better hint, or we need to alter stegbreak so we can try >16 character passphrases. (If someone can point me to an msvc proj file, I'll do it. But a quick scan with google is pulling up nada. and I don't see anything in the src tarball).

[cpip]

Hmm. I realize we're discounting CAPitALLism.org as a hoax, but, just in case, has anyone tried "crackedagain" on the believed-steg pic?

[leova]

seeing as how bungie likes 7's a lot...it might make sense that the password/phrase is 7 characters/words long? perhaps limiting the stegging in such a way might help it find something/nothing faster?

[Pariah]

1 queen
250 drones
20,000 female foragers
40,000 female house-bees
5,000 to 7,000 eggs
7,000 to 11,000 larvae being fed
16,000 to 24,000 larvae developing into adults in sealed cells

These numbers have not been used yet to solve any puzzles have they? Perhaps there is a clue here. One question I have been meaning to ask is about the possible file hidden in the image. In order for the image to not be corrupted doesn't the embedded file have to be <10% the file size of the image. In this case that would make the supposed hidden file <800 bytes. That would be an incredibly small file don't you think? This pretty much rules out any file type other than a plain text document and even then it would have to contain <800 characters including white space. While this doesnt rule out the possiblity of a hidden file, it doesnt make it all that feasable either. Correct me if I am wrong on any of these facts.

[clamatius]

[markoff]