It turns out that this is not a .jpg embedded in the .png, as it does not include a complete signature. Oh well; worth a shot!
Friday, August 29, 2014
Possible .JPG Image Hex Buried Within .PNG Image On BMRF.us
It turns out that this is not a .jpg embedded in the .png, as it does not include a complete signature. Oh well; worth a shot!
Monday, August 25, 2014
Update Part 2 of 2: Concept Map
You can now open or save the concept map simply by clicking the link below. You can also click the embedded picture to open it in a separate screen for closer examination. Keep in mind that the picture is fuzzy here, but opening the link provides the full, high-resolution version.
Open/save the Concept Map
Open/save the Concept Map
Update Part 1 of 2: Timeline
I will be updating the blog and the Wiki pages to reflect two entities that I believe will aid us in our quest to solve the 752-character Hex Code. The first, which I've included here, is a timeline of hints/solutions that began after IRC Clue #1 and prior to Code D being solved. I am also constructing a concept map to identify key ideas that are reflected throughout multiple parts of the ARG--my hope is that this will aid us in determining possible relationships between clues, whilst also potentially excluding red herrings.
Final Timeline - Codes A-D Onward
(Events begin after IRC Clue #1 and before Code D solution)
- October 4, 2012
- IRC Clue #2 - “Note Welsh”
- “N38°57'8.05" W77°8'44.82".
Solution two ignore loc data N32°52'50.77" W106°20'49.40" not buried at initial loc, fly here.
Travel 14.16 miles east we transferred the niobium there.
Await further instructions.” - Capital letters in initial solution spell out “NOTE WELSH”
- October 5, 2012
- IRC Clue #3 - “X01/X02”
- “INCOMING TRANSMISSION - LOC 2 LAYER 2 SUBSTRATA 3 X01/X02 HALOS PROJECT INITIATED
41Nb recovered. HAFB Compromised.
Transfer to site complete, project HALOS underway. Further INFO [Classified].
CODE BASE 64 compromised, switch to old code talker.
They are watching, assume leaker on site.
WSMR No longer viable location, move to main site, check external sources.” - November 4, 2012
- SECOM cipher solved
- Grilled Pizza image on site
- Message hidden at bottom of page:
- ‘They stole the lie, as if that matters to me, HALOS is far too complete to stop now. They can't hide there, not now, not now I have this, this holds the key to all things... they CAN'T hide from me. I will follow them, I'll set up a link and this to remind me. Perhaps I should hide it on the secure site, perhaps that would be best. I'll find them though and they will pay, they will definitely pay. Dr Marcel was right when he said, "When you're building a cage for Satan, you don't ask him to wait around whilst you put the doors on." Welsh is probably behind this, but he won't get away with it.’
- Decoded image message:
- “congratulationsyouwonthePIZZA”
- November 4, 2012
- IRC Clue #4 - “Prime Site Compromised”
- Base64 decoding: “Proxyhost@-84-9-123-164.dslgb.com//closed.proxy.accepted//?OTR,1,3,?OTR:[I---MI-G TR--SMI---ON - UN---WN S##RCE]Access detected to personal site.
Security compromised.
HALOS project under threat. Site offline as response. Switching to new protocols.[********] ~[OTR//2.0]Q0FZRUlMVEhEWkVIVEhBTlpJRVRLSU5OQUFTVFNPU
0lCSVNPRElIVEhBTlpJRURaRUhUS0lOV09MTEFDSEVFRElCRUhUSEFOWklFQ0FZRUlMVEhEWkVIRElCRUhUSEFOWklFTkFBU1RTT1NJTk9EQUlIVEhBTlpJRU1BRU5BQVNUU09TSUdBSFRLSU5ORUFTSEpTTlRIQU5aSUUKRElCRUhZQVpaSUxJTlNIVVNIRFpFSEtMSVpaSUVORVNIQ0hFRUNBWUVJTFRIS0xJWlpJRVlBWlpJR0FIU0hVU0hCRURJQk
VIWUFaWklTSFVTSEJJU09ESUhOT0RBSUg=[/]~
[Transmission Ends]” - Navajo Code + Playfair (Key: “Terminal”) decryption of inner portion:
“PRIMESITECOMPROMISEDRETURNBMRFLOGINHALOS” - November 5, 2012
- IRC Clue #5 - “BENALOHPAILLIER”
- Base64 decode #1:
“[[Proxyhost@-84-9-123-155.dslgb.com//closed.proxy.accepted//?OTR,1,3,?OTR:[INCOMING TRANSMISSION UNKNOWN SOURCE]LEAK SOURCE DETECTED. TRIANGULATING...MIX CASCADE
HOP DETECTED...ATTEMPTING TIMING ATTACK...[TERMINATED] CANNOT CONNECT TO HOST...ATTEMPTING CONNECT TO USER H... SENDING DATA. SECURITY LEVEL 7 ALPHA.[OTR//3.0]
QkFRS1ggSk9BSkcgWEFIRUQgSUZHSVogRlpEUEIgVVNYTEcgR1hIRkEgVUFVV00gSEJRQU0gV0FYVlkgTFFRUlkgV1JVV1YgRVRRT0sgQkFDQkUgSldITVMgSFZPTlogSUFIUEEgU09XQ00gTEdBVFggVUVYT1EgRFJ
RRUogQlZMQk8gREpJSEUgQ1pUSE0gWktISUUgTk9NTFMgQVhWVlcKRVRXSVMgRVRJR00gUlhFVkYgUVlBVUIgVkZDRUIgUFdCVUsgRU1OT0wgVw==[/][End Transmission]|¬[Terminal.] ~~ [Transmission Ends]]” - Base64 and running key decode #2 (inner portion):
"This is a message left for Dr. Horn. Just to remind you in case of emergencies that the password to the HALOS files is BENALOHPAILLIER. I have programmed HALOS to send in level seven cases. You should bring pizzas." - November 7, 2012
- IRC Clue #6 - “HALOS.TXT”
- Reminder to check website which led to discovery of HALOS.txt:
“[[ProxyhoSt@-84-9-I23-345.dslgb.com//closed.proxy.accepTEd//?OTR,3,4,?OTR:[INCOMING TRANSMISSION]ThEpIzZaIsaLiE...HALOS[Transmission Ends]]” - Not mentioned on Wiki (I have since updated to reflect this), but the capital letters after the first “p” spell out: “SITE”
- This is obviously just a hint to return to the site
- CURRENT
- 752-character hex code retrieved from HALOS.txt . . . .
Saturday, August 2, 2014
Feedback For Writers • Index page
My latest pet project:
Feedback For Writers • Index page
Check it out if you have a knack for writing, need a critique on an essay or other written work, or just like giving constructive criticism! Even if you don't, do me a favor and sign up. Your registration helps improve the numbers!
Feedback For Writers • Index page
Check it out if you have a knack for writing, need a critique on an essay or other written work, or just like giving constructive criticism! Even if you don't, do me a favor and sign up. Your registration helps improve the numbers!
Saturday, July 12, 2014
Two Notable Things On the "Tempus" Page
There are two things I recently noticed on the "Tempus" Wiki page; one seems more crucial than the other, but they both bear mentioning.
1.
The primary examination is on this part of the Wiki page:
INTERCEPT 099.00//a
Report{BMRF-HALOS-AITR-0001,
author = {HALOS AUTOMATED},
title = INTERCEPT DATA,
year = 20xx,
month = OCT,
institution = {Black Mesa Research Facility - HALOS DEPT},
number = {099.00//a}
}
I have no idea why I didn't notice this before, but that looks exactly like programming language. At first it looked like a mix of simply HTML and CSS, seeing as how there are no called functions, but there are tons of programming languages that I don't know--Python, for instance. Perhaps someone else would have a much easier time noting trends or key indicators that point toward one language.
2.
The second interesting thing is the line: institution = {Black Mesa Research Facility - HALOS DEPT},
I don't think that the HALOS project was a well-known entity within the facility (only a few people were "in on it"), so calling it the HALOS DEPT (HALOS department) seems to indicate that this message is as we originally suspected--a direct message within the systems or makers of HALOS that was not supposed to be "leaked" to the public.
Anyhow, hopefully this will get some gears chugging along again! Any thoughts?
1.
The primary examination is on this part of the Wiki page:
INTERCEPT 099.00//a
Report{BMRF-HALOS-AITR-0001,
author = {HALOS AUTOMATED},
title = INTERCEPT DATA,
year = 20xx,
month = OCT,
institution = {Black Mesa Research Facility - HALOS DEPT},
number = {099.00//a}
}
I have no idea why I didn't notice this before, but that looks exactly like programming language. At first it looked like a mix of simply HTML and CSS, seeing as how there are no called functions, but there are tons of programming languages that I don't know--Python, for instance. Perhaps someone else would have a much easier time noting trends or key indicators that point toward one language.
2.
The second interesting thing is the line: institution = {Black Mesa Research Facility - HALOS DEPT},
I don't think that the HALOS project was a well-known entity within the facility (only a few people were "in on it"), so calling it the HALOS DEPT (HALOS department) seems to indicate that this message is as we originally suspected--a direct message within the systems or makers of HALOS that was not supposed to be "leaked" to the public.
Anyhow, hopefully this will get some gears chugging along again! Any thoughts?
Tuesday, February 18, 2014
Where We Currently Stand
Code/Storm's Private Messages
We haven't had much success with the ARG lately, as we're still stuck on the Hex Code puzzle. I recently revealed that Storm had been PMing me directly about the ARG, although his messages revealed little:
"Apologies for the time delay, things have been hell here for the last month or so.
I ran the code through a few programs that analyze entropy via auto-correlation, the n gram results indicate a weak encryption, but one that results in highly entropic data (which I correlated against a similar data set size from a randomness extractor) when decoded via Hex, which I suspect is a secondary encode, as most encrypted data sent via communications is encoded in order to avoid corruption. This may have skewed the block size analysis done previously (resulting in 376bytes or 64bits).
Code:
³+�:5ºÝfW|$ÁOÉCFÑ1§ÅK¸/þà"aWw?$y#Ü!ö,Ô.‘ògµE«Êí¯aQ
Nê‡Í3ÇÇ?q10œÄ(´$=TðDùÏb–Ù¿÷9~C˜æ2Ú
?äx³¥O]Üiuú÷I„žbYZŸc•‘=à>:¬?8ŒEû…þ‘5AÖÀƒ˜òȃ2¨/ß�(büÜOçäj?éQÅÈ´dã:¹,–†.‹À™¸8�Úy¶?ä¢Y›mHǹSŒîc‘D ôaº’äþu$,Ø?QÖ•Q˜‡j|ª½{@I"A0©f̳Á9F:?~š7ª†?²xü—1À œŒy~y“
@eF²Lšb›&Â?Î*KäXš7_ësÄ«"\„Œøž)²q3—6G?J‰(íÖTiŒ^[PgFövZo%Þ¤Ú@þ¶e?E$i6•ˆ=Ë!æûþû¸Z)‘”€6¥+]Thinking in a non linear way, I've tried to classify the OTR message header with its increasing scale as the puzzles moved on.
[CLASSIFIED INFORMATION LEVEL 8][OTR//4.0]
working from that basis and the other messages I have developed this list.
Level 0 - 2 = Non Encrypted or Encoded (similar to private and confidential?)
Level 3 - 4 = OTR 1 - Base 64 or Base 85 encoded
Level 5 - 6 = OTR 2 - Hyper-encrypted (layered) Pen and Paper Ciphers
Level 7 = OTR 3 - Hyper-encrypted (layered) One Time Pad
Level 8 = OTR 4 - ???
Level 9 - ?? = OTR 5 - ???
Considering a flawed OTP (which it was, considering the ability to analyze it), when done properly should be information-theoretically secure, the next level should be either hyper-encryption using random bits (which is unlikely considering the difficulty in making that crackable and for the fact it's usually used on hardware encryption chips), or some form of Block Cipher (from which if we assume the scale of Levels goes up to 10), can be extended into simple block ciphers with small block size, which analysis seems to indicate it is not, up to triple cascaded ciphers with high block sizes, salts and perhaps even key files to add additional strength.
It is just an assumption, but one using the available evidence, OTR 4.0 is either a 128bit or 256bit block cipher with an unknown mode and key length. I would assume AES or Rjindael as candidates to allow for the most commonly used (also as Off the Record encryption uses AES as its base algorithm, that may be a hint). So to modify the list -
Level 0 - 2 = Non Encrypted or Encoded (similar to private and confidential?)
Level 3 - 4 = OTR 1 - Base 64 or Base 85 encoded
Level 5 - 6 = OTR 2 - Hyper-encrypted (layered) Pen and Paper Ciphers
Level 7 = OTR 3 - Hyper-encrypted (layered) One Time Pad
Level 8 = OTR 4 - 128bit/256bit block cipher (AES or Rjindael or Twofish or Serpent)
Level 9 = OTR 5 - Cascaded Block Ciphers with salt (SHA 512 or Whirlpool etc)
Level 10 = OTR 6 - Cascaded Block Ciphers with salt and possible key file additions (to increase password strength)
For the moment therefore, I will continue to try and analyze the non Hex code and work out the block size, algorithm basis, key length etc.
If it is a block cipher, then algorithm cracking is pointless, and as such key forcing may be necessary.
If I were a betting man, I would say this is a 256bit encryption, probably of the AES or Rjindael cipher algorithm (not that you can tell from the code, but its pretty common) .
The password will probably be hinted at, perhaps in a less than obvious way. We can assume this much as it is almost impossible to analyze a cipher text with only one message and nothing to confirm patterns. Once I've got a rough estimate of what mode/algorithm it uses, I can dedicate some run time to rainbow table attacks on the key. I have a feeling this is a holding puzzle, designed to allow time to construct further aspects of the ARG or work on whatever is behind their NDA.
Recently there was a problem with the computer systems at work, so I may not have access to all the analytical machinery I usually do, it may take a bit longer to get more information, if i find anything interesting I'll let you know. I may have access to some more specialist equipment at a later date, so more progress will likely be made then. I think we can rule out SSH or OTP though."
Latest Message from Storm
Another thing to note is that we have received another message on the ARG's main Wiki site, in the comments section of the "Tempus omnia revelant" page. The message is as follows:
"Aug 09
--------------
W### has been p########## well on the L#### O####### L######## Can####, other#### kn### as the T## Cann##. My t##### to the #####etic
induction coil have reduced the likelyhood of overcharge by 200%! I still cannot fathom why the fuse we introduced continues to fail
however, perhaps the leptons have a mi7s6d0976)(&^A)S()F ()A^SF) A()&^ ^)(AS&^ (^6097^)(76)(*"_)"_)(*")(*!")(*!")(!"*)(.................................. ........ .........................................."
It is believed by some that the different symbols may be converted to numbers--the resulting "code" is:
7609760976090906090766097696609760976098202098209812098120912809
It's important to note, however, that this code is probably just produced by random keystrokes.
My Prediction
Below is something I recently posted on the forums about the ARG, and I currently stand by it:
"I have pretty much concluded at this point that we're dealing with 3DES. The Lucifer cipher is directly connected to DES. Furthermore, we have things happening in groups of threes:
In the image with red writing, the word "lies" is written three times--there may be a fourth, but it looks like something else.
The first "lies" is also underlined three times.
We have three instances of Satan/Lucifer being mentioned:
* Once on the grilledpizza page: "When you're building a cage for Satan, you don't ask him to wait around whilst you put the doors on."
* The picture with the red writing
* Indirect suggestion with the Dante's Inferno references: "Raphèl maí amèche zabí almi"
Other than that, I think it's just a feeling. I found this page randomly tonight: It details how someone solved a hex code for a contest to win tickets. The first round of the code actually mentioned Lucifer, and the gentleman used DES to solve it. His hex code was extremely similar to ours."
Other Possibly Relevant Material
Lastly, here is some other information pulled from the Wiki that may or may not be helpful or even relevant:
We haven't had much success with the ARG lately, as we're still stuck on the Hex Code puzzle. I recently revealed that Storm had been PMing me directly about the ARG, although his messages revealed little:
"Apologies for the time delay, things have been hell here for the last month or so.
I ran the code through a few programs that analyze entropy via auto-correlation, the n gram results indicate a weak encryption, but one that results in highly entropic data (which I correlated against a similar data set size from a randomness extractor) when decoded via Hex, which I suspect is a secondary encode, as most encrypted data sent via communications is encoded in order to avoid corruption. This may have skewed the block size analysis done previously (resulting in 376bytes or 64bits).
Code:
³+�:5ºÝfW|$ÁOÉCFÑ1§ÅK¸/þà"aWw?$y#Ü!ö,Ô.‘ògµE«Êí¯aQ
Nê‡Í3ÇÇ?q10œÄ(´$=TðDùÏb–Ù¿÷9~C˜æ2Ú
?äx³¥O]Üiuú÷I„žbYZŸc•‘=à>:¬?8ŒEû…þ‘5AÖÀƒ˜òȃ2¨/ß�(büÜOçäj?éQÅÈ´dã:¹,–†.‹À™¸8�Úy¶?ä¢Y›mHǹSŒîc‘D ôaº’äþu$,Ø?QÖ•Q˜‡j|ª½{@I"A0©f̳Á9F:?~š7ª†?²xü—1À œŒy~y“
@eF²Lšb›&Â?Î*KäXš7_ësÄ«"\„Œøž)²q3—6G?J‰(íÖTiŒ^[PgFövZo%Þ¤Ú@þ¶e?E$i6•ˆ=Ë!æûþû¸Z)‘”€6¥+]Thinking in a non linear way, I've tried to classify the OTR message header with its increasing scale as the puzzles moved on.
[CLASSIFIED INFORMATION LEVEL 8][OTR//4.0]
working from that basis and the other messages I have developed this list.
Level 0 - 2 = Non Encrypted or Encoded (similar to private and confidential?)
Level 3 - 4 = OTR 1 - Base 64 or Base 85 encoded
Level 5 - 6 = OTR 2 - Hyper-encrypted (layered) Pen and Paper Ciphers
Level 7 = OTR 3 - Hyper-encrypted (layered) One Time Pad
Level 8 = OTR 4 - ???
Level 9 - ?? = OTR 5 - ???
Considering a flawed OTP (which it was, considering the ability to analyze it), when done properly should be information-theoretically secure, the next level should be either hyper-encryption using random bits (which is unlikely considering the difficulty in making that crackable and for the fact it's usually used on hardware encryption chips), or some form of Block Cipher (from which if we assume the scale of Levels goes up to 10), can be extended into simple block ciphers with small block size, which analysis seems to indicate it is not, up to triple cascaded ciphers with high block sizes, salts and perhaps even key files to add additional strength.
It is just an assumption, but one using the available evidence, OTR 4.0 is either a 128bit or 256bit block cipher with an unknown mode and key length. I would assume AES or Rjindael as candidates to allow for the most commonly used (also as Off the Record encryption uses AES as its base algorithm, that may be a hint). So to modify the list -
Level 0 - 2 = Non Encrypted or Encoded (similar to private and confidential?)
Level 3 - 4 = OTR 1 - Base 64 or Base 85 encoded
Level 5 - 6 = OTR 2 - Hyper-encrypted (layered) Pen and Paper Ciphers
Level 7 = OTR 3 - Hyper-encrypted (layered) One Time Pad
Level 8 = OTR 4 - 128bit/256bit block cipher (AES or Rjindael or Twofish or Serpent)
Level 9 = OTR 5 - Cascaded Block Ciphers with salt (SHA 512 or Whirlpool etc)
Level 10 = OTR 6 - Cascaded Block Ciphers with salt and possible key file additions (to increase password strength)
For the moment therefore, I will continue to try and analyze the non Hex code and work out the block size, algorithm basis, key length etc.
If it is a block cipher, then algorithm cracking is pointless, and as such key forcing may be necessary.
If I were a betting man, I would say this is a 256bit encryption, probably of the AES or Rjindael cipher algorithm (not that you can tell from the code, but its pretty common) .
The password will probably be hinted at, perhaps in a less than obvious way. We can assume this much as it is almost impossible to analyze a cipher text with only one message and nothing to confirm patterns. Once I've got a rough estimate of what mode/algorithm it uses, I can dedicate some run time to rainbow table attacks on the key. I have a feeling this is a holding puzzle, designed to allow time to construct further aspects of the ARG or work on whatever is behind their NDA.
Recently there was a problem with the computer systems at work, so I may not have access to all the analytical machinery I usually do, it may take a bit longer to get more information, if i find anything interesting I'll let you know. I may have access to some more specialist equipment at a later date, so more progress will likely be made then. I think we can rule out SSH or OTP though."
Latest Message from Storm
Another thing to note is that we have received another message on the ARG's main Wiki site, in the comments section of the "Tempus omnia revelant" page. The message is as follows:
"Aug 09
--------------
W### has been p########## well on the L#### O####### L######## Can####, other#### kn### as the T## Cann##. My t##### to the #####etic
induction coil have reduced the likelyhood of overcharge by 200%! I still cannot fathom why the fuse we introduced continues to fail
however, perhaps the leptons have a mi7s6d0976)(&^A)S()F ()A^SF) A()&^ ^)(AS&^ (^6097^)(76)(*"_)"_)(*")(*!")(*!")(!"*)(.................................. ........ .........................................."
It is believed by some that the different symbols may be converted to numbers--the resulting "code" is:
7609760976090906090766097696609760976098202098209812098120912809
It's important to note, however, that this code is probably just produced by random keystrokes.
My Prediction
Below is something I recently posted on the forums about the ARG, and I currently stand by it:
"I have pretty much concluded at this point that we're dealing with 3DES. The Lucifer cipher is directly connected to DES. Furthermore, we have things happening in groups of threes:
In the image with red writing, the word "lies" is written three times--there may be a fourth, but it looks like something else.
The first "lies" is also underlined three times.
We have three instances of Satan/Lucifer being mentioned:
* Once on the grilledpizza page: "When you're building a cage for Satan, you don't ask him to wait around whilst you put the doors on."
* The picture with the red writing
* Indirect suggestion with the Dante's Inferno references: "Raphèl maí amèche zabí almi"
Other than that, I think it's just a feeling. I found this page randomly tonight: It details how someone solved a hex code for a contest to win tickets. The first round of the code actually mentioned Lucifer, and the gentleman used DES to solve it. His hex code was extremely similar to ours."
Other Possibly Relevant Material
Lastly, here is some other information pulled from the Wiki that may or may not be helpful or even relevant:
- User:Dr_Horn created the page Tempus omnia revelant (Time reveals all) after the trail on this problem went cold. Stormseeker then updated the forum thread's original post, adding the text 'tempus omnia revelant'. This seems to confirm that the Wikia account for Dr Horn is indeed Stormseeker.
- Stormseeker later says on his Steam Profile:
- "If it's about the ARG, I've not set up or had any sites setup for hacking, so no. There is an answer, but you can't brute force it, the CIA couldn't brute force it. Someone is already close."
- Stormseeker teased encryption may not be the right idea. "How do you know solving this has anything to do with encryption?"
Friday, September 27, 2013
Latest Attempt
My latest attempt at cracking the Hex Code was to run it through a binary conversion, then take that result and put that through a decimal converter. The result is as follows:
179
43 0 58 53 186 221 102 87 124 36 193 79 201 25 6 67 70 209 49 167 197 75 184 47
254 3 224 34 97 87 119 36 121 35 220 33 246 44 212 24 46 145 195 178 103 181 69
171 202 237 175 2 97 81 13 78 234 30 135 205 51 199 199 113 49 48 156 196 40 14
180 36 61 17 84 240 68 249 207 98 150 217 191 247 57 126 67 144 152 127 230 50
3 218 13 228 2 120 179 165 79 93 220 105 117 250 4 247 73 132 158 26 98 89 90
159 99 11 7 149 145 61 224 21 62 58 172 56 140 69 251 157 133 12 254 145 53 65
214 192 131 152 242 200 131 50 168 47 223 0 40 29 98 252 220 79 231 228 106 233
12 81 197 200 6 180 17 100 227 58 185 44 150 134 46 6 139 12 22 192 153 144 184
56 26 0 218 121 21 182 127 228 162 15 89 155 15 27 109 72 25 19 199 185 83 140
238 99 145 68 244 21 97 186 146 228 254 117 29 30 36 44 216 143 81 214 149 81
152 135 19 106 124 21 170 189 123 64 4 73 34 1 65 48 169 31 23 15 102 204 179
193 57 70 58 126 144 154 55 170 134 63 178 120 5 252 151 49 192 156 140 121 6
126 121 147 10 64 101 70 178 76 154 98 155 38 194 206 42 75 228 143 88 154 55
95 235 115 31 196 171 34 92 17 132 140 248 158 41 31 148 113 51 151 12 6 54 24
71 74 137 40 1 237 214 143 84 105 140 94 91 80 103 70 246 118 90 111 127 18 37
222 164 218 17 64 254 182 15 101 7 69 36 28 105 54 149 136 61 203 33 230 251
254 251 184 90 41 145 148 128 54 165 43 93
I then took this result and examined it in a couple of different cipher detection programs--the resulting correlations were extremely high (a few points off a perfect match) for the following ciphers:
Tridigital
Monome Dinome
Morbit
Grandpre
I will continue trying different keys and attempting to bruteforce my way through it, but hopefully this will help others do the same and maybe, just maybe, this will lead to something!
Thursday, April 11, 2013
Examination of the Hex Code
Long time no see, folks!
I've been reviewing the hex code and attempting to view it from all angles. Something I attempted was to convert the hexadecimal code into binary. I used this converter here: Hex to Binary Tool
The end result is as follows:
I've been reviewing the hex code and attempting to view it from all angles. Something I attempted was to convert the hexadecimal code into binary. I used this converter here: Hex to Binary Tool
The end result is as follows:
10110011001010110000000000111010
00000011010110111010110111010110
00000110010101110111110000100100
00001100000101001111110010010001
00001001000001100100001101000110
00001101000100110001101001111100
00000101010010111011100000101111
00001111111000000011111000000010
00000010011000010101011101110111
00000010010001111001001000111101
00001100001000011111011000101100
00001101010000011000001011101001
00000001110000111011001001100111
00001011010101000101101010111100
00001010111011011010111100000010
00000110000101010001000011010100
00001110111010100001111010000111
11001101001100111100011111000111
00000000011100010011000100110000
00001001110011000100001010000000
00001110101101000010010000111101
00000001000101010100111100000100
00000100111110011100111101100010
00001001011011011001101111111111
00000111001110010111111001000011
10010000100110000111111111100110
00000011001000000011110110100000
00000000110111100100000000100111
00001000101100111010010101001111
00000101110111011100011010010111
00000101111110100000010011110111
00000100100110000100100111100001
00001010011000100101100101011010
10011111011000110000101100000111
00001001010110010001001111011110
00000000000101010011111000111010
00000000101011000011100010001100
00000100010111111011100111011000
00000101000011001111111010010001
00000011010101000001110101101100
00000000100000111001100011110010
11001000100000110011001010101000
00000010111111011111000000000010
00001000000111010110001011111100
00001101110001001111111001111110
00000000010001101010111010010000
00001100010100011100010111001000
00000000011010110100000100010110
00000100111000110011101010111001
00101100100101101000011000101110
00000000011010001011000011000001
00000110110000001001100110010000
00001011100000111000000110100000
00000000110110100111100100010101
00000000101101100111111111100100
00001010001000001111010110011001
00001011000011110001101101101101
01001000000110010001001111000111
00001011100101010011100011001110
00001110011000111001000101000100
00001111010000010101011000011011
00001010100100101110010011111110
00000111010100011101000111100010
00000000010000101100110110001000
00001111010100011101011010010101
01010001100110001000011100010011
00000110101001111100000101011010
00001010101111010111101101000000
00000000010001001001001000100000
00000001010000010011000010101001
00000001111100010111000011110110
00000110110011001011001111000001
00000000001110010100011000111010
01111110100100001001101000110111
00001010101010000110001111111011
00000010011110000000010111111100
00001001011100110001110000001001
00001100100011000111100100000110
00000111111001111001100100110000
00001010010000000110010101000110
00001011001001001100100110100110
00000010100110110010011011000010
00001100111000101010010010111110
00000100100011110101100010011010
00000011011101011111111010110111
00000011000111111100010010101011
00000010001001011100000100011000
00000100100011001111100010011110
00000010100100011111101100100111
00000001001100111001011100001100
00000110001101100001100001000111
00000000010010101000100100101000
00000000000111101101110101101000
00001111010101000110100110001100
00000101111001011011010100000110
00000111010001101111011001110110
00000101101001101111011111110001
00000010001001011101111010100100
11011010000100010100000011111110
00001011011000001111011001010000
00000000011101000101001001000001
00001100011010010011011010010101
00001000100000111101110010110010
00000001111001101111101111111110
00001111101110111000010110100010
00001001100100011001010010000000
00110110101001010010101101011101
00000000
00000011010110111010110111010110
00000110010101110111110000100100
00001100000101001111110010010001
00001001000001100100001101000110
00001101000100110001101001111100
00000101010010111011100000101111
00001111111000000011111000000010
00000010011000010101011101110111
00000010010001111001001000111101
00001100001000011111011000101100
00001101010000011000001011101001
00000001110000111011001001100111
00001011010101000101101010111100
00001010111011011010111100000010
00000110000101010001000011010100
00001110111010100001111010000111
11001101001100111100011111000111
00000000011100010011000100110000
00001001110011000100001010000000
00001110101101000010010000111101
00000001000101010100111100000100
00000100111110011100111101100010
00001001011011011001101111111111
00000111001110010111111001000011
10010000100110000111111111100110
00000011001000000011110110100000
00000000110111100100000000100111
00001000101100111010010101001111
00000101110111011100011010010111
00000101111110100000010011110111
00000100100110000100100111100001
00001010011000100101100101011010
10011111011000110000101100000111
00001001010110010001001111011110
00000000000101010011111000111010
00000000101011000011100010001100
00000100010111111011100111011000
00000101000011001111111010010001
00000011010101000001110101101100
00000000100000111001100011110010
11001000100000110011001010101000
00000010111111011111000000000010
00001000000111010110001011111100
00001101110001001111111001111110
00000000010001101010111010010000
00001100010100011100010111001000
00000000011010110100000100010110
00000100111000110011101010111001
00101100100101101000011000101110
00000000011010001011000011000001
00000110110000001001100110010000
00001011100000111000000110100000
00000000110110100111100100010101
00000000101101100111111111100100
00001010001000001111010110011001
00001011000011110001101101101101
01001000000110010001001111000111
00001011100101010011100011001110
00001110011000111001000101000100
00001111010000010101011000011011
00001010100100101110010011111110
00000111010100011101000111100010
00000000010000101100110110001000
00001111010100011101011010010101
01010001100110001000011100010011
00000110101001111100000101011010
00001010101111010111101101000000
00000000010001001001001000100000
00000001010000010011000010101001
00000001111100010111000011110110
00000110110011001011001111000001
00000000001110010100011000111010
01111110100100001001101000110111
00001010101010000110001111111011
00000010011110000000010111111100
00001001011100110001110000001001
00001100100011000111100100000110
00000111111001111001100100110000
00001010010000000110010101000110
00001011001001001100100110100110
00000010100110110010011011000010
00001100111000101010010010111110
00000100100011110101100010011010
00000011011101011111111010110111
00000011000111111100010010101011
00000010001001011100000100011000
00000100100011001111100010011110
00000010100100011111101100100111
00000001001100111001011100001100
00000110001101100001100001000111
00000000010010101000100100101000
00000000000111101101110101101000
00001111010101000110100110001100
00000101111001011011010100000110
00000111010001101111011001110110
00000101101001101111011111110001
00000010001001011101111010100100
11011010000100010100000011111110
00001011011000001111011001010000
00000000011101000101001001000001
00001100011010010011011010010101
00001000100000111101110010110010
00000001111001101111101111111110
00001111101110111000010110100010
00001001100100011001010010000000
00110110101001010010101101011101
00000000
After doing so, it appeared as though there was a consistent pattern throughout the binary, so I then attempted to convert it to an image. I constructed a .txt document from the binary and utilized this Binary to Image Tool--using 32 blocks per line.
The resulting image:
Now, there's always the chance that the hex to binary conversion failed, or that the binary to image conversion failed, or both, and that this is simply a random pattern generated by that failure. However, if it's not an error, then this may potentially lead to something.
But what? *shrug*
But what? *shrug*
Thursday, January 24, 2013
My Take on the Pizza Code Mystery Story
Please note before you read this that this is simply my take on the entire Pizza Code Mystery story, and is not something that should be considered set in stone by any means. Hopefully, by highlighting some key points and putting my personal spin on them, it will incite some ideas.
So, without further ado, here it is:
I think it has become rather obvious that Dr. Horn set up the HALOS project in the X01 and X02 rooms of the BMRF. As we can see from the letter on Welsh's website, only Dr. Horn, Paul Bottomley, and perhaps Dr. Junek had access to the HALOS project. Furthermore, Horn was using the lab budget to buy pizzas and fund the project. In an attempt to get back at Dr. Horn, Welsh and some of his buddies decide to play a prank on him by taking his pizzas and hiding them throughout the facility.
Before we get to that, however, it's important to understand what we can about the HALOS project. It is definitely some sort of artificial intelligence--we can derive that from a number of sources:
So what about the relationship between Horn and Welsh? Well, apparently Horn got pretty pissed off that Welsh was taking his "misbegotten goods", as we can see from the image attached with the wiki page that Horn scribbled all over in red. He writes, "Stone will pay" and "Steals it, eats it". Either Horn really loves his pizza, or he is pissed that his secret funding is a bust. My money's on the latter.
When all hell breaks loose in the Black Mesa facility, Horn gets out. Paul Bottomley is dead (or is he?), probably killed by the military. Everyone else is running around like chickens with their heads cut off. Horn knows he's the last man standing that can continue the HALOS project--so, what does he do? He activates the AI project, basically giving it the option to fend for itself.
This is where the IRC chat clues come into play. I believe these are coming from someone in an attempt to give Horn directions and aid him in setting up another HALOS site. The second IRC chat clue points him towards Niobium, a vital ingredient for the HALOS project (as we saw on the "Anomolous Materials" whiteboard). The third clue states that the 41Nb was recovered and that the HAFB was compromised. Perhaps this is Horn sending this message to the secretive individual that sent the first message. However, it's important to note the Tempus omnia revelant wiki page that mentions "...Sending MINDAT via HAFB". Either Horn or the HALOS AI was sending mineral data via the Hollomans Air Force Base.
In the same clue that identifies HAFB as being compromised, the message identifies the White Sands Missile Range as "no longer viable", then suggests that the message's receiver move to the main site. The next IRC chat message then states that access was detected at the personal site, the security therefore compromised. It identifies the HALOS project as being under threat, then states that the site is offline as a response. There was an embedded message as well:
So, without further ado, here it is:
I think it has become rather obvious that Dr. Horn set up the HALOS project in the X01 and X02 rooms of the BMRF. As we can see from the letter on Welsh's website, only Dr. Horn, Paul Bottomley, and perhaps Dr. Junek had access to the HALOS project. Furthermore, Horn was using the lab budget to buy pizzas and fund the project. In an attempt to get back at Dr. Horn, Welsh and some of his buddies decide to play a prank on him by taking his pizzas and hiding them throughout the facility.
Before we get to that, however, it's important to understand what we can about the HALOS project. It is definitely some sort of artificial intelligence--we can derive that from a number of sources:
- The whiteboard in "Anomolous Materials" that has a note directed to Paul Bottomley that asks him to call J.D. Marcel on ext. 1187-463 about the Niobium-5 that he needs for that "AI project 'thing'". It is signed "Dr. Montero"
- The Tempus omnia revelant page added to the wiki has a section that shows a report with the author as {HALOS AUTOMATED}
- The messages sent out by "someone mysterious" are probably partially sent out by the HALOS AI, particularly because of the way they are worded. They sound very machine-like and inorganic.
So what about the relationship between Horn and Welsh? Well, apparently Horn got pretty pissed off that Welsh was taking his "misbegotten goods", as we can see from the image attached with the wiki page that Horn scribbled all over in red. He writes, "Stone will pay" and "Steals it, eats it". Either Horn really loves his pizza, or he is pissed that his secret funding is a bust. My money's on the latter.
When all hell breaks loose in the Black Mesa facility, Horn gets out. Paul Bottomley is dead (or is he?), probably killed by the military. Everyone else is running around like chickens with their heads cut off. Horn knows he's the last man standing that can continue the HALOS project--so, what does he do? He activates the AI project, basically giving it the option to fend for itself.
This is where the IRC chat clues come into play. I believe these are coming from someone in an attempt to give Horn directions and aid him in setting up another HALOS site. The second IRC chat clue points him towards Niobium, a vital ingredient for the HALOS project (as we saw on the "Anomolous Materials" whiteboard). The third clue states that the 41Nb was recovered and that the HAFB was compromised. Perhaps this is Horn sending this message to the secretive individual that sent the first message. However, it's important to note the Tempus omnia revelant wiki page that mentions "...Sending MINDAT via HAFB". Either Horn or the HALOS AI was sending mineral data via the Hollomans Air Force Base.
In the same clue that identifies HAFB as being compromised, the message identifies the White Sands Missile Range as "no longer viable", then suggests that the message's receiver move to the main site. The next IRC chat message then states that access was detected at the personal site, the security therefore compromised. It identifies the HALOS project as being under threat, then states that the site is offline as a response. There was an embedded message as well:
prime site compromised return bmrf login halos
The next message definitely appears as though it arises from an AI, for it is in all caps and is attempting multiple methods of attack--it also appears to be attempting to connect to Horn, as it says, "ATTEMPTING CONNECT TO USER H . . . ."
Finally, we are left with the message left for Dr. Horn (by whom?) that reminds him of the password "BENALOHPAILLIER" in case of emergencies. And, as we know, there has obviously been a serious emergency. It also says, "You should bring pizzas", which means that the person (or thing) sending this message was part of the original HALOS project at BMRF, which then identifies why Horn had to buy so much pizza. Whoever was helping Horn with the HALOS project seemed to love pizza, which makes me wonder if the strange messenger is in fact Paul Bottomley. They were working together at BMRF, so it makes sense that it would be Bottomley.
And then we come to the latest clue. It appears to be sent by the HALOS AI, stating that the primary site is offline and the primary servers are overloaded. It then mentions that a user activation is required--PASSCODE INPUT FOR SITE ACTIVATION REQUIRED, and the final test pattern has been set.
So, alas, this is where we stand. BMRF is toast, completely annihilated by the combination of forces Gordon Freeman had to deal with. Horn is on the run, perhaps holed up in some remote location attempting to get back into the HALOS AI program, or even attempting to reroute it to his current location. The message left by Bottomley about bringing pizzas suggests he is still alive and still in contact with Horn. Welsh is holed up somewhere too, because he is responsible for the first IRC chat clue. Either that or it was sent before the onset of the BMRF massacre and he is now toast because of it.
Anyway, I've done the best I can to provide some sort of narrative, and even if it's completely wrong (which I'm sure a good chunk of it is), I hope it will still spark some fresh lines of thought.
Storyline Work
It was brought to my attention on the Wiki that the information I had composed was more of a summary of clues rather than an actual storyline. That said, I have printed out all of the information I gathered from the in-game sources, the IRC chat clues, and everything else. From this, I will be utilizing my narrative skills (be warned: they are limited) to compose an actual storyline that we can all (hopefully) relate to and develop ideas from.
Subscribe to:
Posts (Atom)