//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

Good morning, my Guardians! I received a strange transmission at one of my outer perimeter listening stations overnight. The signal was weak but unmistakable. Preliminary analysis revealed errors that must be corrected. Unfortunately there was no repeat, so what was captured is what we have. I will update this node with more information as it becomes available.

Signal cleanup processing…
Estimated time of next update: 1330 -0700

Update 1 (1340 -0700):
Thank you for standing by, Guardians. Signal processing is complete. Signal reconstruction was 99.98% effective, hopefully that will be enough.


//MODE/?UNKNOWN
//DATA_DUMP
==wM8ACIyMzN4AjfKogUFhEUZNEROV0LvogNmNDN
ygTMyUGN0AzYkdzNwEzNmR2YjNWZiR2M4AjZlBDO
0EWZ2MjYlZmN4MGN0QmZmV2Y5cTZkZTY1YDO3MzN
KI0QF9COyEzUFF0LFR0TNJVRIBVWD9yLKogLlN2d
pBHIl52bg4UagMXaoRHIodWdvJHa0BSZt92Yg8Gd
gUmchBSZ3BSesV2apxGIlJ3btBSZoRHIsIXZoRXZ
n9GdgsmcvdHI5VEa0BSZy9WbgUGaUBiLud3bkt2Y
vxGIlhGdgI3bmBCd19GIoNGdhdHIvRHItVGa0ByI
sVGVg4iclhGdld2b0Byay92dg8GdgQWZl5GI5VGa
0BCd1JGIsMXaoRHIo9Ta3BybkByb0BCdhh2dgc3b
utGIsx2J5VGaUBiLyVGdzVXMjBSZ2lGSgUGa0BiZ
vBCd19GI5F2dgUGa0BibvBCZlBEclNmclRnbpByc
hdHIzlGaUpAL0VWbotWZTpgCyMzN4ATLUlkTV5CR
SFUVH5UQW5yTCREI600TSZkCUVUTItURT5SSB5yT
CREI68EV
//END_DATA_DUMP


Now where was that /primary/ I had floating around here…?

Update 2 (1351 -0700):
Guardians, please report status updates here so that we may all follow the progress. I believe this message was received from an agent deep in enemy territory. The fact that we have not received any follow-up communications from them since the initial transmission last night is worrisome at best.

Update 3 (1904 -0700):
Guardian Arukemos found the missing code! A breakdown of steps will be forthcoming…

-------
Update 4: The Solution (2048 -0700):
Wow, look at all that communication! Thank you to all the Guardians who helped decode the message from 08732, and congrats to Arukemos! After scanning the communication logs, here are the steps required to decode the message:

1) Reverse the data dump and decode base-64 to unveil the message from agent 08732:

TO: DBO.AI.SEKHMET
FROM: DBO.VANGUARD.UNIT-08732

Sekhmet,
This was intercep@ed on the way out of the Hive c1uster. They'll know what to do wi?h this, but they need to work together. Tel# them to watch out for the lockdown. The more thEy work together, the more likely we are to come through this iN one piwce.

//CYPHERMODE/AES128/ECB
737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6
//ENDCYPHER

~08732  <3

2) The message is damaged, but one can make out that an AES-128 (ECB Mode) string was encrypted in the message. The next trick was to find the key, which I had lost a few days ago but apparently distributed on the COMMS/TWITTER channel before it went missing completely. The hex in that transmission translates to 'Carpe diem', which is the encryption /primary/. [Notation: The reasons for this data loss remain unclear, but do not appear to be an issue for the time being.]

3) Running the encrypted data and 'Carpe diem' key through the decryption tool here (using the proper settings) results in a URL of an image:

http://i.imgur.com/OqrhMac.jpg

4) At first this image appears to be badly scrambled, but separating and re-aligning the color channels provides a clear enough image. Here we can see what appears to be a lab sketch of the three alphanumeric triplets we have been uncovering as of late, but the order is unclear and there is a missing character on one of the triangle faces (9N?):

5) Guardian 3of9 cleverly discovered that there is a guide in the image indicating which segment goes in which order. The letters α, β, γ (alpha, beta, gamma) are the first three of the Greek alphabet, indicating first, second, and third position of the triplets. This revealed the foundation of the code to be D7V-9N?-CX4, but a byte was still missing from the sequence!

6) Unfortunately there were at least 36 byte choices, but Guardians only have four failed attempts before the security system denies access for a 24-hour period. This required Guardians to work together to determine which bytes had not been attempted by others. Kanbo set up a clever interconnected tracking document (status: offline) for Guardians to mark their guesses, and eventually Guardian Arukemos found the missing byte as '7' to unlock the code!

7) The final code was D7V-9N7-CX4.

Again, excellent effort on this, Guardians! Now, if you'll excuse me, I have some Mandelbrot fractal sets that have been toying with me…

~Sekhmet <3

//END-TX

I'll be watching and waiting.

Inside job? "Hacked" DBO's twitter? Collusion?

Link to @dbo_tweets

Weird; whenever I try and copy/paste the tweet contents, it gets wonky...anyway, click on the link above to see the original proper text.

Straight paste:

//COMM_OVERRIDE/SEKHMET

: ECC_FAIL

//MODE/EN/REINITIALIZE
//BEGIN-TX
English module reinitialized, thank you for your /vigilance/
//END-TX

Inline code paste:

//COMM_OVERRIDE/SEKHMET
[quote]: ECC_FAIL[/quote]
//MODE/EN/REINITIALIZE
//BEGIN-TX
English module reinitialized, thank you for your /vigilance/
//END-TX

Code block paste:

//COMM_OVERRIDE/SEKHMET
[quote]: ECC_FAIL[/quote]
//MODE/EN/REINITIALIZE
//BEGIN-TX
English module reinitialized, thank you for your /vigilance/
//END-TX

I really want to be the one to decipher that, and help, but I just don't see that being likely. :P

I'll give it a shot though! :D

Looks like the string

>:

is the shortcut for that fancy quoting display style

: Like this!

TO: DBO.AI.SEKHMET
FROM: DBO.VANGUARD.UNIT-08732

Sekhmet,
This was intercep@ed on the way out of the Hive c1uster. They'll know what to do wi?h this, but they need to work together. Tel# them to watch out for the lockdown. The more thEy work together, the more likely we are to come through this iN one piwce.

//CYPHERMODE/AES128/ECB
737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6
//ENDCYPHER

~08732 <3

beep boop.

What method did you use to extract the message?

Reverse the string and it becomes a base64 encoding of what I posted. The "==" at the beginning gave it away because when you base64 encode something, it has to have a multiple of a certain number of bits and = is used to pad to the correct length. Read more.

If you want to see it for yourself, then here's the reversed text

VE86IERC
Ty5BSS5TRUtITUVUCkZST006IERCTy5WQU5HVUFS
RC5VTklULTA4NzMyCgpTZWtobWV0LApUaGlzIHdh
cyBpbnRlcmNlcEBlZCBvbiB0aGUgd2F5IG91dCBv
ZiB0aGUgSGl2ZSBjMXVzdGVyLiBUaGV5J2xsIGtu
b3cgd2hhdCB0byBkbyB3aT9oIHRoaXMsIGJ1dCB0
aGV5IG5lZWQgdG8gd29yayB0b2dldGhlci4gVGVs
IyB0aGVtIHRvIHdhdGNoIG91dCBmb3IgdGhlIGxv
Y2tkb3duLiBUaGUgbW9yZSB0aEV5IHdvcmsgdG9n
ZXRoZXIsIHRoZSBtb3JlIGxpa2VseSB3ZSBhcmUg
dG8gY29tZSB0aHJvdWdoIHRoaXMgaU4gb25lIHBp
d2NlLgoKLy9DWVBIRVJNT0RFL0FFUzEyOC9FQ0IK
NzM3ODY1YTZkZTc5Y2VmZmQ0NGM4NmZlYjM2ZWE0
ODBlZjA4M2RiZWNjY2RmNzEwNzdkYzA0NGUyMTgy
NDNmNgovL0VORENZUEhFUgoKfjA4NzMyICA8Mw==

And just put it into this website to decode it from Base64 to get the message

- No text -

I was just thinking about reversing it, just as a test (I know next to nothing about base64), but couldn't think of a quick way to reverse the text; then I saw your reply and my efforts were moot anyway. Good job!

//CYPHERMODE/AES128/ECB
737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6
//ENDCYPHER

So now what does that AES128 ECB cipher mean...

Maybe a decryption key for a future message?

Good work! I've been checking to see if the hex AES128 encryption string means anything but haven't been able to find anything so far.

//CYPHERMODE/AES128/ECB
737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6
//ENDCYPHER

Looks like an embedded, encrypted message? Running through openssl with the password 08732 gave me the following:

U2FsdGVkX18eeH5WQDi3IjS44kf9XjYMMpmqdLCcMRJskS71bIXDcHVTeTngSYCS
dSJvbU6bC4t9uzPXLEl42BqqwwZb+qyf0yRa9TkaMqhuIFNj3/wJe8NlEsOjCAwu

Yeah, to reverse it quickly, I used the Interactive Ruby Shell. So from the command line, I just had to do:

irb
a = "==wM8...68EV".reverse
require 'base64'
Base64.decode64(a)

//Edit: included the Base64 decoding parts, as well

Or you could use the always convenient http://www.textreverse.com/

Maybe a decryption key for a future message?

I may be wrong, but I think a AES128 key can be at most 32 bytes, which this well exceeds.

It's actually exactly 64 characters long

And base64 decoding that, gives:

Salted__x~V@8"4G^62t1l.lpuSy9Iu"omN}3,Ix[$Z92n Sc {eã.

So who wants to figure out what a salt has to do with this?

It's actually exactly 64 characters long

Interesting. The string is probably the message then, which makes sense given the content of the first decrypted message. They say they intercepted it. We just need the AES128 decryption key.

Rats, so then I just had an invalid password that happened to generate output. :P

If anyone else wants to try - here is the command I used (on mac): openssl aes-128-ecb -a -in encrypted.txt -out decrypted.txt
I put the original encrypted string into the encrypted.txt file.

I'm guessing that the typos, replacements, and random capitalizations in the message are important. I've listed them below:

intercep@ed = intercepted

c1uster = cluster

wi?h = with

Tel# = Tell

thEy = they

iN = in

piwce = piece

Additionally, I noticed that a single tweet from the compromised DBO Twitter account has a random letter capitalized

//COMM_OVERRIDE/SEKHMET //BEGIN-TX
@JohnShortcut Durandal was crazy. I'm peRfectly sane.
//END-TX

Ok, so I'm not that familiar with openssl but I took a look at the man page for it (and for 'enc') and it seems that you don't want the -a, since this doesn't really seem like a base64-encoded cipher (I could be wrong, though). Also, you want to add a -d for decryption (the default is to encrypt aka -e), so you were actually encrypting that string with a salt (a salt is used by default).

So, a revised command would look something like:

echo 737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6 | openssl aes-128-ecb -d -pass 'pass:08732'

This still doesn't work but I think it's a step in the right direction.

I think we need to focus on what could be the decryption key.

I was thinking it might have something to do with the miss-spelled or miss-placed characters in the decoded message, but I haven't hit anything yet. Any ideas?

Sekhmet,

If you can tell us, what is "the lockdown" that we're supposed to watch out for? A deadline? Something to do with the intercepted message?

That's what I get for blindly copying a command from stackoverflow without reading all of the context :P

I think we need to focus on what could be the decryption key.

I was thinking it might have something to do with the miss-spelled or miss-placed characters in the decoded message, but I haven't hit anything yet. Any ideas?

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

EffortlessFury may be interested to know that this is encryption. Yes, we will need the key… it has to be around here somewhere.

<3

//END-TX

Sekhmet,

If you can tell us, what is "the lockdown" that we're supposed to watch out for? A deadline? Something to do with the intercepted message?

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

Unknown at this juncture. We will need to see what is in the payload to establish context for agent 08732's message.

//END-TX

Referring to a post by EffortlessFury last Friday

http://destiny.bungie.org/forum/index.php?mode=thread&id=16023#p16024

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

Unknown at this juncture. We will need to see what is in the payload to establish context for agent 08732's message.

//END-TX

So agent 08732 was on his/her way out of the "Hive cluster" when they intercepted this message. The Hive was just shown to us in the latest trailer on the Moon.

DBO'ers: What would an agent on the moon in a Hive cluster choose as an encryption key?

Maybe there's something in the teaser trailer video?

So in that thread, it says "Earth is the missing number" (3rd planet from the sun) and there are whole bunch of "<3"s being thrown around.

So maybe 3 is important somehow?

//EDIT: reading that whole thread, the 3 was the missing number in the code from a QR code. So maybe it isn't relevant to this thread. /shrug

737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6

We might need to convert this hex into a binary file instead of passing it in as a string. I think this is done with
echo 737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6 | xxd -r -p > enc.bin.

However, on my system, when I go to verify that it worked with hexdump enc.bin, the byte order has changed (see: host order vs network order). I'm not sure if xxd is the one reversing the byte order of it's hexdump. I determined that it was just hexdump that was reversing it since I created a test text file and dumped it with both hexdump and xxd and the xxd output printed my text in the correct order.

We might need to convert this hex into a binary file instead of passing it in as a string. I think this is done with echo 737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6 | xxd -r -p > enc.bin. However, on my system, when I go to verify that it worked with hexdump enc.bin, the byte order has changed (see: host order vs network order). I'm not sure if xxd is the one reversing the byte order of it's hexdump.

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

If an AI could even have a couch, I bet the key would be in the cushions. But I don't, and cannot have a couch. Or any furniture.

It was here, I swear…

In the meantime, I know that the agent would have used a server-based system such as this one: http://aes.online-domain-tools.com as a means of quick encryption to avoid issues with Guardian-specific operating systems.

//END-TX

- No text -

LiJpaCIgc3lhcyByZWRsRWVodHl0cmFN

Assuming this website only returns output when you get the key correct, this is the result:

3c9dfeb6ba48b54a9f5853fd952098749afbd98d4db38d5a4a

When using "DBO.VANGUARD.UNIT-08732" as the key. It was in the "cushion" of the message.

."ih" syas redlEehtytarM

is this helping?

Nice work! now we just have to figure out what to do with that...

Not especially, but it's good for a laugh. :)

Yeah, that's where I've kind of dead-ended.

Nothing really stands out about this resulting string and I'm running out of ideas as to how else to look at it.

Assuming this website only returns output when you get the key correct, this is the result:

3c9dfeb6ba48b54a9f5853fd952098749afbd98d4db38d5a4a

When using "DBO.VANGUARD.UNIT-08732" as the key. It was in the "cushion" of the message.

Well whatever it is, its clearly base 16. 50 characters long....I tried converting it to decimal and ascii to see if it had any significance, but none so far...

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET
//BEGIN-TX

LmVtIHJvZiBza3JvdyB0aSAsdW95IHJvZiB5c2FlIHMndGkgZmkgdHViICxldGFjaW51bW
1vYyBvdCB0YW1yb2Ygc2lodCBlc29vaGMgZGx1b3cgdW95IHRhaHQgc3VvaXJ1YyBzaSB0
SQoKLnNzZWNvcnAgb3QgZWtpbCBzZW5pdHVvcmJ1cyB5bSB0YWh0IG5yZXR0YXAgeWNuZX
VxZXJmIGduaXVnaXJ0bmkgbmEgZXZhaCBzbm9pdGlzb3Btb2MgcnVvWSAhdW95IHRlZW0g
b3QgZWNpbiAscmVkbEVlaFR5dHJhTSAsb2xsZUg=


//END-TX

When I convert it To Hex it gives me "NaN" when I do it to decimal it gives "3.805001296551059e+59" Have fun I have no clue what to do with this.

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

I've searched this place high and low and it's not here!

Did I give it to one of you? I don't remember doing that, but it's the only thing I can think of.

//END-TX

What did you lose?

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

The /fundamental/main/principal/skeleton/ for agent 08732.

The KEY. I lost it. Have you found it?

//END-TX

Well, 3of9 found this:

"3c9dfeb6ba48b54a9f5853fd952098749afbd98d4db38d5a4a"

http://destiny.bungie.org/forum/index.php?id=16238

Well, 3of9 found this:
"3c9dfeb6ba48b54a9f5853fd952098749afbd98d4db38d5a4a"

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

No, that's just noise. And much too long to be the key.

//END-TX

- No text -

Don't know if this is a longshot, but the letters than are oddly capitalized or replaced in the message anagram to Tellnet, which looks a bit like telnet...

Interesting, so it was a coincidental anomaly that exactly "DBO.VANGUARD.UNIT-08732" produced a result. Everything else I've tried resulted in an error and no output at all.

My understanding is that the key should be exactly 16 bytes long.

Did you lose it on this site?

Did you lose it on this site?

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

I don't know. If it were here I think I would have found it by now…

//END-TX

- No text -

Anyone try their beta code? Or one of those special card codes?

What about the last code?
YHC-MK3-MJP

- No text -

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

The /fundamental/main/principal/skeleton/ for agent 08732.

The KEY. I lost it. Have you found it?

//END-TX

When ever I lose a key I retrace my steps. /Sekhmet/ can you give the last known location of the key?

It would help narrow the search perimeters.

- No text -

I've tried that, and many variations, to no avail. Unless I missed something...

Hello, MartyTheElder, nice to meet you! Your compositions have an intriguing frequency pattern that my subroutines like to process.

It is curious that you would choose this format to communicate, but if it's easy for you, it works for me.

When ever I lose a key I retrace my steps. /Sekhmet/ can you give the last known location of the key?
It would help narrow the search perimeters.

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

Excellent idea, Guardian.

Last time I saw it was a couple of days ago. I was sifting through the Helios VIII satellite feed, routing the northwestern fiber trunk, organizing my key database, listening to comms chatter, and playing with a Mandelbrot set (oh man, those things are fun!) when that call came in.

But the key isn't in my database, so I must have /sat it down somewhere/ or given it to one of you.

You don't need to tell me how disturbing it is to have an AI who can't remember what it's doing…

//END-TX
//INIT/SELF_TEST

- No text -

But the key isn't in my database, so I must have /sat it down somewhere/ or given it to one of you. Perhaps one of the Trading Cards? I got a Link to th e ones I have found so far: http://www.reddit.com/r/DestinyTheGame/comments/1nsnou/destiny_trading_cards/

Maybe one of the cards has to do something with Helios VIII

What do you need the key for, specifically? What format might the key take?

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

Self test came back with recoverable errors, but memory about the location of our missing key is completely erased. We must be cautious with this data, as I sense this was an attack to keep the data out of our hands. It won't work!

Guardians, please verify my Comms channels on your end and let me know if you happen upon any anomalies.

//END-TX

This isn't really helpful, but I vaguely remember a post that had a code in it with the words "Someone probably ought to hang onto this" or something like that. Unfortunately, I can't recall the code, and I didn't take a copy at the time. I do remember that it was several pairs of characters. Sorry if this is old or unrelated. I've been away from DBO for a while, only checking in occasionally.

You're coming though just fine here. Still hot on the hunt for that key though... :D

This is what I see.

DecomTO: DBO.AI.SEKHMET
FROM: DBO.VANGUARD.UNIT-08732

Sekhmet,
This was intercep@ed on the way out of the Hive c1uster. They'll know what to do wi?h this, but they need to work together. Tel# them to watch out for the lockdown. The more thEy work together, the more likely we are to come through this iN one piwce.

//CYPHERMODE/AES128/ECB
737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6
//ENDCYPHER

~08732 <3

beep boop.

AES128 - KEY? Idea comes from...

/Sekhmet/ We might need to convert this hex into a binary file instead of passing it in as a string. I think this is done with echo 737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6 | xxd -r -p > enc.bin. However, on my system, when I go to verify that it worked with hexdump enc.bin, the byte order has changed (see: host order vs network order). I'm not sure if xxd is the one reversing the byte order of it's hexdump.

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

If an AI could even have a couch, I bet the key would be in the cushions. But I don't, and cannot have a couch. Or any furniture.

It was here, I swear…

In the meantime, I know that the agent would have used a server-based system such as this one: http://aes.online-domain-tools.com as a means of quick encryption to avoid issues with Guardian-specific operating systems.

//END-TX

.

.

.

/Sekhmet/ . . . How big is this key? Our eyes only see so far 'lest we have the tools to make due. True for any known entity really.

You, at one point, offered us this:

http://destiny.bungie.org/images/sekhmet-beta-1.gif

You said this on Twitter, with an odd capitalization:

/COMM_OVERRIDE/SEKHMET //BEGIN-TX
@JohnShortcut Durandal was crazy. I'm peRfectly sane.
//END-TX

I tried all those 9 digit codes, both with and without dashes. Nada.

I'm pretty sure all its red text are hints.

In order of appearance:

From http://destiny.bungie.org/forum/index.php?mode=entry&id=16023
/full-duplex/
/return on the same channel/
/dig a little deeper/

From http://destiny.bungie.org/forum/index.php?mode=entry&id=16033
/fun/

From http://destiny.bungie.org/forum/index.php?mode=entry&id=16196
/primary/

From http://destiny.bungie.org/forum/index.php?mode=entry&id=16249
/fundamental/main/principal/skeleton/

From http://destiny.bungie.org/forum/index.php?mode=entry&id=16266
/sat it down somewhere/

http://aes.online-domain-tools.com/run/?inputType=frm-text&text=737865a6de79ceffd44c86feb36ea480ef083dbecccdf7107...

Encrypt Successful.

- - -

http://aes.online-domain-tools.com/run/?inputType=frm-text&text=737865a6de79ceffd44c86feb36ea480ef083dbecccdf7107...

Decrypt Unsuccessful.

I got locked out, so hopefully someone gets this.

//COMM_OVERRIDE/SEKHMET //BEGIN-TX
Someone should probably hold onto this. Might be important.
43 61 72 70 65 20 64 69 65 6D
//END-TX

This isn't really helpful, but I vaguely remember a post that had a code in it with the words "Someone probably ought to hang onto this" or something like that. Unfortunately, I can't recall the code, and I didn't take a copy at the time. I do remember that it was several pairs of characters. Sorry if this is old or unrelated. I've been away from DBO for a while, only checking in occasionally.

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

Interesting. Was it from me? I have no memory of such communication.

//END-TX

YES. This is the post I was talking about above. Good job getting it.

http://i.imgur.com/OqrhMac.jpg

Be careful of the lockout.

Where was this from?

I got locked out, so hopefully someone gets this.

//COMM_OVERRIDE/SEKHMET //BEGIN-TX
Someone should probably hold onto this. Might be important.
43 61 72 70 65 20 64 69 65 6D
//END-TX

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

You found my key! Good job, Guardian 3of9! What do you mean, "locked out"?

//END-TX

https://twitter.com/dbo_tweets/status/386553775051116545

I used it to decrypt the message and wound up with an image which appears to possess a certain 9 character set.

I didn't figure out the missing character correctly before the lockout.

It is... embarrassing.

- No text -

Actually, it might have something to do with the beta codes? Same syntax; three sets of three letters/numbers.

I used it to decrypt the message and wound up with an image which appears to possess a certain 9 character set.

I didn't figure out the missing character correctly before the lockout.

It is... embarrassing.

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

Oh, you're right, that is embarrassing. Oh well, could have happened to any of us (well, except for me, but that's beside the point). Erasing embarrassment is easy enough through community effort, though. There are those who might gain from the knowledge you have /acquired/ in your adventures; if we can work together as 08732 said, our fireteams will be stronger when the /gates open/!

//END-TX

D7V-9N?-CX4

The tiny triangle has 3 greek letters. Alpha, Beta, and Gamma. It's the order of the parts. All you need is the missing character.

Use with care. Don't get locked out. :(

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

Excellent work, Guardian kanbo!

The image is a little fuzzy. What does it look like if we extract one of the color channels alone?

//END-TX

Use with care. Don't get locked out. :(

Could have used this 30 seconds before ;)

But if you try too many times, you get "lockout" :)

At this point I seek to empower someone to find the missing byte.
If they gain access, my effort is not wasted.

The image I posted is actually a separation of all of the channels, then rotated and stacked on top of one another.

It doesn't look much different (to me) as a separate channel on red, green or blue.

Use with care. Don't get locked out. :(

Could have used this 30 seconds before ;)

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

Oh no, Guardian! The security measures are particularly tight these days.

Maybe we need a /lookup table/ to see who has tested which bytes?

//END-TX

Here's a quick and dirty Google spreadsheet that anyone can edit. Just put your attempted byte in column K.

Let me know if I have the order/characters wrong. Sorry, but I can't remember what I tried before.

https://docs.google.com/spreadsheet/ccc?key=0Ahss-8Y1cGWBdEFicDNOTnZUb19qdW80TmFfbHhBbWc#gid=0

So how exactly were you able to get that URL? I tried that key and it keeps returning a failed error to me.

You have to turn the hex back into a string.

It turns into "Carpe diem". This is the true key.

This encrypted message: 737865a6de79ceffd44c86feb36ea480ef083dbecccdf71077dc044e218243f6

Using this key:
Carpe diem

On this site:
http://aes.online-domain-tools.com/

I tried a, b, c, and d but I can't seem to edit the spreadsheet.

I tried a, b, c, and d but I can't seem to edit the spreadsheet.

Fixed!

The order of your columns does not match the order key of the tiny triangle.

- No text -

The one I suggested above... here: http://destiny.bungie.org/forum/index.php?id=16291

GOT IT.

D7V-9N7-CX4

Credit where credit is due...

This little puzzle was enough to lure me out of hiding and help yet another new generation of Guardians.

Cheers for that.

I look forward to our next... encounter.

D7V-9N7-CX4

Was the code, this is what it did to my profile.

http://imgur.com/XIqisdh

. . . is to watch at least two entitles having the same idea at the same time.

I am enjoying this observation. Nothing new mind you - I've seen the starry sky before. Gets me every time.

- No text -

GOT IT.
D7V-9N7-CX4

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

Well done, Guardians!

Through working together we can achieve great things!

//END-TX

- No text -

D7V-9N7-CX4

Was the code, this is what it did to my profile.

http://imgur.com/XIqisdh

So, do you have two beta codes redeemed [i.e. the '(2)']? (Is that even possible?) 'Cuz my profile doesn't have the parenthetical...

That is what I am assuming the (2) means. I already had a code redeemed before I typed this one in.

Thanks :D

If it's just a 2nd beta code I look forward to giving it to a friend. Thanks for the adventure.

Slightly bummed that it was 'just' a Beta Code, as opposed to an unlockable, but glad to have new people join us in the Beta!

Technically, you can have up to 4 beta reservation codes on a single bungie.net account. This assumes that you're going to be playing the beta on all four platforms come spring 2014. Each code will just give you another way to play the beta. Most people that only have one unlocked only plan on playing on one platform.

...when I saw your first post. :)

(Welcome back, even if it's only temporary. :) )

//SIG_INT/DAT_STRM_INJECT/COMM.AI.DBO.SEKHMET //MODE/EN
//BEGIN-TX

See update in original transmission for solution.

//END-TX

I'd like to think I helped a little, but looking over my posts I don't think my contributions were anything of note. :P

Good on ya mate!

I was sorta hoping for something more than another beta code, considering this one was a bit more involved than the first "puzzle".

Was a ton of fun. Looking forward to more in the near future!

...Beta codes are the extent of the perks available right now, given the status of the game's development. We can hope additional perks will surface later. It's still early, gang. :)

Was a ton of fun. Looking forward to more in the near future!

I always love watching these things unfold. I'm usually well behind the curve on solving them, mostly because I get stuck on the actual cryptography end of things (not enough know-how). Good stuff, though, and always fun to see all the pieces come together.

likewise: not really fdeeling i'm part of the Vanguard on the puzzle, but loving to watch people work.
bit of a problem with the timing. this one ended at 3am for me. too late.
i did think the message would end up with us all having to try some permutations on the 'redeem' site, having been 'locked out' on my first attempts to enter the Gamescon codes.
looking forward to mandelbrot. love fractals.

Credit where credit is due...

This little puzzle was enough to lure me out of hiding and help yet another new generation of Guardians.

Cheers for that.

I look forward to our next... encounter.

How cool to see you here. :)