It simply corresponds with “Dr. Horn”
04 = D
18 = R
08 = H
15 = O
18 = R
14 = N
Thanks. Also, I know about the reply button, but my PC’s not letting me.
Maybe a security software or something.
Ok, I tried it, but no joy. 
Maybe the names of the people involved have something to do with it.
OK, I may be way off base here, but…“givenkey” would also be eight bytes.
where is the password supposed to be put? sorry I have no clue.
^On the vice command-line.
vice is a command-line tool. On Windows, you’ll have to run it in a Command Prompt window. The specific command-line syntax depends on whether you are using the Source SDK version or the standalone version of vice. However, a Windows binary (executable) for the vice tool is not readily available. Someone is going to have to build it, or you can try the version available here. However, as I mentioned earlier, a VirusTotal scan result of the .exe file looked suspect.
I’m attaching the Linux version I used with the modifications I made to it that adds an option to set the ICE encryption level.
However, it looks like we’re heading into the password hell again just as with the other ciphers / tools we’ve been trying.
Also, keep in mind that the ICE cipher / vice-tool idea is just another one on our long list of theories. The “evidence” supporting this, if any, is just as vague and sketchy as that for every other idea we’ve had so far. But because of the Source SDK connection, it kind of felt like a promising idea. But, I don’t know. The fact that the standard vice tool only uses keys of 8 bytes (or characters because the tool is limited to using keys that consist of characters that you can type on the command-line) is sort of contradicted by stormseeker’s “The CIA couldn’t brute force it.” comment. That’s why I thought perhaps we needed to increase the ICE encryption level in order to use longer keys. To my knowledge, this encryption level thing is something that’s unique to the ICE cipher.
EDIT 2014-09-19: I now believe this is a dead end. In order to prevent people from wasting their time with it, I’ve deleted the attachment along with the instructions on how to build/use the tool.
dont wurrie guys, time will reveal all
This is probably unsolvable right now, either because we are not skilled enough for this, because it is imposible solve, or because we missed something. Anyway, lets just keep trying. Flavrans9 did an impressive work compilating things on the wiki. I read everything again and the only thing that seems weird is the name Code_. Why "" after Code? To imply that 0418 was him? But he already said that as 0418 that he was Code_. Might that be the clue to the password or key? Turning the password cases into their position number on the alphabet? It seems a bit “meta” and the start of an epileptic tree search, but I’ll check it up as soon as I have time available.
By the way, I’m 99.9% sure he’s stormseeker, he said as 0418_ that he participated on ARG Torment by Greengecko, on the UNforums there’s a puzzle trail thread for that ARG and one of the posters is stormseeker. I think I might have already posted this, but I’m not completly sure.
https://forums.unfiction.com/forums/viewtopic.php?t=19001&start=45
Gruntfuttock is also on that thread, he’s stormseeker’s friend, Dr. Paul Bottomley in the game. Anyway, I tried to use the wayback machine to see the ARG, but the image files are not archived and there’s not much to see
https://web.archive.org/web/20070812065153/https://www.grngecko.com/getintro.html?
It could be unsolvable at the moment, and time will reveal all, including the solution. Also, does “Vox populi vox Dei” mean anything? It translates to “the voice of the populace is the voice of the Deity” or more commonly “the voice of the people is the voice of god” It is the first sentence on the Tempus Omnia Revelant page. Perhaps it means that the voice (posts) of someone on the forums is actually the voice of god (Storm Seeker), besides which people we already know are him. Maybe it means to review the evidence brought to the table just before the page’s creation, as if we missed something obvious. Also, HALOS could be a reference to this webcomic: https://xkcd.com/375/ Ok, maybe not but I feel like I’m on the the right track!
Maybe it tells of somebody who, if they gain control of HALOS, will be unstoppable. After all, we really don’t know the extent of the HALOS program. It could run all through the facility… Or even further than that.
Maybe HALOS has something to do with HAL 9000 from “2001: A space odyssey”? HAL was an AI, and HALOS is an AI too. Just my wild guess…
Thanks. 
It’s not like I did some massive work on the wiki. But yes, I recently added a page about Stormseeker, where I compiled a list of ARG-related quotes by Stormseeker, explained the link found between 0418_08151814 and Dr_Horn (and hence the likely connection to Stormseeker), and quoted the PMs 0418_08151814 sent to Gunsrequiem. Other pages written by me are the BMRF.us and DALsystems pages. But I’ve also been touching up some other pages.
But there’s still a lot more work that needs to and can be done on the wiki, like, for instance, writing a page about what we know about the Tempus omnia revelant message so far (which I’ve been meaning to do but have not got around to yet).
If any of you have any comments or suggestions about any of my additions or edits made to the wiki, please let me know. Thanks.
(Note: I always do my edits on the wiki logged in as Flavrans9, so I can’t take credit for edits made by anonymous/not-logged-in users.)[/SIZE]
I just looked at the pages. Thanks for the creating of them, because most of that information I didnt know.
I noticed something weird on the code sent by 0418_ to guns. I thought it might be some kind of modified code with a 1337 51º341< message on it, due to this section “(íÖTiŒ”, it resembles the word notice too much, or at least that is what it seems to me. So, I started comparing the code with the original 752hexcode. Then, after deleting the hex pairs that don’t have a visual representation onscreen, it seems that 0418_ added some “?” ramdomly. Here they are: the original and the code sent by 0418_
³+[COLOR='Lime']00:5ºÝfW|$ÁOÉ[COLOR='Lime']1906CFÑ1§ÅK¸/þ[COLOR='Lime']03à"aWw$y#Ü!ö,Ô[COLOR='Lime']182E‘ògµE«Êí¯[COLOR='Lime']02aQ[COLOR='Lime']0DNê[COLOR='Lime']1E‡Í3ÇÇq10œÄ([COLOR='Lime']0E´$=[COLOR='Lime']11TðDùÏb–Ù¿÷9~C[COLOR='Lime']90˜[COLOR='Lime']7Fæ2[COLOR='Lime']03Ú[COLOR='Lime']0Dä[COLOR='Lime']02x³¥O]Üiuú[COLOR='Lime']04÷I„ž[COLOR='Lime']1AbYZŸc[COLOR='Lime']0B07•‘=à[COLOR='Lime']15>:¬8ŒEû[COLOR='Lime']9D…[COLOR='Lime']0Cþ‘5AÖÀƒ˜òȃ2¨/ß[COLOR='Lime']00([COLOR='Lime']1DbüÜOçäjé[COLOR='Lime']0CQÅÈ[COLOR='Lime']06´[COLOR='Lime']11dã:¹,–†[COLOR='Lime']2E06‹[COLOR='Lime']0C16À™[COLOR='Lime']90¸8[COLOR='Lime']1A00Úy[COLOR='Lime']15¶[COLOR='Lime']7Fä¢[COLOR='Lime']0FY›[COLOR='Lime']0F1BmH[COLOR='Lime']1913ǹSŒîc‘Dô[COLOR='Lime']15aº’äþu[COLOR='Lime']1D1E$,Ø[COLOR='Lime']8FQÖ•Q˜‡[COLOR='Lime']13j|[COLOR='Lime']15ª½{@[COLOR='Lime']04I"[COLOR='Lime']01A0©[COLOR='Lime']1F170Ff̳Á9F:~[COLOR='Lime']90š7ª†?²x[COLOR='Lime']05ü—1ÀœŒy[COLOR='Lime']06~y“[COLOR='Lime']0A@eF²Lšb›&ÂÎ*Kä[COLOR='Lime']8FXš7_ës[COLOR='Lime']1FÄ«"\[COLOR='Lime']11„Œøž)[COLOR='Lime']1F²q3—[COLOR='Lime']0C066[COLOR='Lime']18GJ‰([COLOR='Lime']01íÖ[COLOR='Lime']8FTiŒ^[PgFövZo[COLOR='Lime']7F12%Þ¤Ú[COLOR='Lime']11@þ¶[COLOR='Lime']0Fe[COLOR='Lime']07E$[COLOR='Lime']1Ci6•ˆ=Ë!æûþû¸Z)‘”€6¥+]³+�:5ºÝfW|$ÁOÉCFÑ1§ÅK¸/þà"aWw?$y#Ü!ö,Ô.‘ògµE«Êí¯aQNê‡Í3ÇÇ?q10œÄ(´$=TðDùÏb–Ù¿÷9~C[COLOR='Lime']90˜[COLOR='Lime']7Fæ2Ú?äx³¥O]Üiuú÷I„žbYZŸc•‘=à>:¬?8ŒEû[COLOR='Lime']9D…þ‘5AÖÀƒ˜òȃ2¨/ß�(büÜOçäj?éQÅÈ´dã:¹,–†.‹À™[COLOR='Lime']90¸8�Úy¶[COLOR='Lime']7F?ä¢Y›mHǹSŒîc‘D ôaº’äþu$,Ø?[COLOR='Lime']8FQÖ•Q˜‡j|ª½{@I"A0©f̳Á9F:?~[COLOR='Lime']90š7ª†?²xü—1ÀœŒy~y“@eF²Lšb›&Â?Î*KäXš7_ësÄ«"\„Œøž)²q3—6G?J‰(íÖTiŒ^[PgFövZo%Þ¤Ú@þ¶e?E$i6•ˆ=Ë!æûþû¸Z)‘”€6¥+]The [COLOR=‘Lime’]Lime numbers and cases are the ones that cannot be represented. These interrogations � appear due to copying and pasting an unrepresentable case, nothing weird, but,on the original “ÇÇq10”, and suddenly, on the code sent by 0418 “ÇÇ?q10”. There’s no unrepresentable hex code there. It was added, on purpose I would imagine. It happens in other sections of the code. Also, a “?” was added in the place of some unprintable hex pairs, but not on most cases, that had to be done “by hand”.
Then, on the 0418_ code, the only unprintable hex pairs are:
8F,90,9D=Nothing, literally, there is no printable or control character associated.
7F=Delete
I don’t really know if this would happen due to copy pasting the code after converting it to ASCII, or there is some intention to it.
In any case, it seems the message was padded with interrogations randomly just to make up for the unprintable characters, the reason to do this goes over my head, but it may have some meaning behind it.
That’s odd. Those stray question marks have been inserted in front of every 32nd character as they appear in the original hex code.
Look at the hex dump of the original hex code:
And here’s the code sent by 0418_ to Guns with the stray question marks and the characters they precede highlighted:
You’ll see that the question marks appear in front of the characters at (hex) addresses 20, 40, 60, 80, a0, etc.
I can’t see how the question marks would appear like this, unless they were placed there on purpose. Maybe it’s a hint.
That pattern could indicate that it actually happened when converting the hex code to ASCII, if the hex editor was set to show 32 bytes per row, might it have added the “?” instead of the carriage return at the end of each row? I never got that to happen when converting hex to ASCII, but I don’t know if it is even possible. The code was copy pasted at least two times, once when 0418_ sent it to Guns, and again when Guns posted it here.
It is strange still, it’s an ASCII “?”, it’s the equivalent to a 3F in hex, while carriage return is 0D. This might actually be worth looking into.
The interregation marks divide the code in 32 bytes long segments, but for the last one that is 24 bytes long. Maybe the block length is 256 bits? The only block cipher I know that supports that block length is RIJNDAEL, I don’t remember if GOST also supports that block length, but I think it does not and I can’t find the article I read about it. So, RIJNDAEL, using 256 block size, probably using ecb mode. Now, if I recall correctly, ecb does not work in stream mode, so the last block would not be complete, but the message would decode no problem till that last section.
Still, we need the password. It could be on the lol cannon whiteboard, I tried most words on it, but some things I cannot understand properly, like the numbers just above the electronic configuration of the Promethium. It something like 47PM3 2-8-15-23-8-2, but I’m not completly sure if it is 7PM or 70M, or if there is an L or a 4 before the first 7. The 15 might not be a 15 but a 13 or 18, I can’t see it
Nevertheless, we should probably try to know for sure if the “?” are intentional, can somebody confirm that they would not appear instead of the carriage returns when copy pasting?
Edit: There is a similarity between rooms X01 and X02 and thestormseeker.com. From stormseeker info on his steam profile “My Portfolio Site (Still under construction)” and the budgets whiteboards, “Be aware location is still under construction - wear a hard hat”. We also know that the HALOS project takes place in rooms x01 and x02, and the halos file was found on thestormseeker.com/thepizzaisalie/. Maybe there is another halos file on the site, or something that is needed to solve the code, but that we have not found yet. We know from the grilled pizza puzzle, that there is a secure site where he was going to hide something that “holds the key to all things”.
This is a snippet of the HTML from the original reply by 0418_ (Storm), including the “[code]” tags he included:
³+�: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¥+]
My money is on the "?"s being intentional.
Also, if you view the “Reply” option of this post, you can see the complete original format in which it was sent to me; the skewed spacing is also intact–whether intentional or otherwise, that’s how it came.
Taking the code in this way the result is slightly different, it takes the carriage returns and the line feeds, 0D 0A, but it doesn’t change the fact that the ? appear just before the characters on the 20,40,60… positions of the original 752code. So we think that this is intentional, then, what does this indicate?
The only difference now from what Gunsrequiem posted the first time are two spaces that must have been inserted there by the forum software to prevent long continuous strings messing up the layout. Those spaces are not inserted when you use the [tt][code][/tt] tags. Also, the lines break where they break because of the two CRs (0d) and one LF (0a) in the original hex code.
The foreign "?"s have been inserted in between groups of characters, where each group belongs to a 32 byte block in the raw code. The groups in 0418_'s code are not 32 characters long because some of the unrepresentable characters have been lost in the conversion to ASCII/Unicode (note that there is one “?” that is supposed to be there since it’s in the original hex code).
So what does this mean? In terms of modern cryptography this could be a very clear and unmistakable hint that we are dealing with a block cipher with a block size of 256 bits (32 bytes), which could be Rijndael-256 (I can’t help but wonder if the DALsystems login terminal came up as a hint towards Rijndael, since DAL ~ dael). The only other 256 bit block cipher I’ve found so far is a cipher called Threefish.
If the block size is 256 bits, then the last block is incomplete. This could either mean that the last block has been truncated, or that one of the cipher modes CTR, CFB or OFB was used. Interestingly, the OTR (Off The Record) protocol uses the CTR (Counter) mode, and 0418_ does mention the OTR protocol in his PM to Guns.
The 32 byte grouping could also mean that the key size is 256 bits.
In case we’re not dealing with modern cryptography, then what could this 32 byte grouping mean? One possibility could be that the code is just compressed text where the bytes have been scrambled using classic cryptography or puzzle techniques. In order to solve it, maybe we have to arrange the hex in 32 byte groups, and then do some columnar transpositions or something. We should check if there could be compression headers or file markers up or down a column when we view the code in 32 byte groups.
Here’s a hex dump of the code using 32 bytes per row:
[CODE]Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F 10 11 12 13 14 15 16 17 18 19 1A 1B 1C 1D 1E 1F
00000000 B3 2B 00 3A 35 BA DD 66 57 7C 24 C1 4F C9 19 06 43 46 D1 31 A7 C5 4B B8 2F FE 03 E0 22 61 57 77 ³+.:5ºÝfW|$ÁOÉ…CFÑ1§ÅK¸/þ.à"aWw
00000020 24 79 23 DC 21 F6 2C D4 18 2E 91 C3 B2 67 B5 45 AB CA ED AF 02 61 51 0D 4E EA 1E 87 CD 33 C7 C7 $y#Ü!ö,Ô…‘ògµE«Êí¯.aQ.Nê.‡Í3ÇÇ
00000040 71 31 30 9C C4 28 0E B4 24 3D 11 54 F0 44 F9 CF 62 96 D9 BF F7 39 7E 43 90 98 7F E6 32 03 DA 0D q10œÄ(.´$=.TðDùÏb–Ù¿÷9~C.˜.æ2.Ú.
00000060 E4 02 78 B3 A5 4F 5D DC 69 75 FA 04 F7 49 84 9E 1A 62 59 5A 9F 63 0B 07 95 91 3D E0 15 3E 3A AC ä.x³¥O]Üiuú.÷I„ž.bYZŸc…•‘=à.>:¬
00000080 38 8C 45 FB 9D 85 0C FE 91 35 41 D6 C0 83 98 F2 C8 83 32 A8 2F DF 00 28 1D 62 FC DC 4F E7 E4 6A 8ŒEû.….þ‘5AÖÀƒ˜òȃ2¨/ß.(.büÜOçäj
000000A0 E9 0C 51 C5 C8 06 B4 11 64 E3 3A B9 2C 96 86 2E 06 8B 0C 16 C0 99 90 B8 38 1A 00 DA 79 15 B6 7F é.QÅÈ.´.dã:¹,–†…‹…À™.¸8…Úy.¶.
000000C0 E4 A2 0F 59 9B 0F 1B 6D 48 19 13 C7 B9 53 8C EE 63 91 44 F4 15 61 BA 92 E4 FE 75 1D 1E 24 2C D8 ä¢.Y›…mH…ǹSŒîc‘Dô.aº’äþu…$,Ø
000000E0 8F 51 D6 95 51 98 87 13 6A 7C 15 AA BD 7B 40 04 49 22 01 41 30 A9 1F 17 0F 66 CC B3 C1 39 46 3A .QÖ•Q˜‡.j|.ª½{@.I".A0©…f̳Á9F:
00000100 7E 90 9A 37 AA 86 3F B2 78 05 FC 97 31 C0 9C 8C 79 06 7E 79 93 0A 40 65 46 B2 4C 9A 62 9B 26 C2 ~.š7ª†?²x.ü—1ÀœŒy.~y“.@eF²Lšb›&Â
00000120 CE 2A 4B E4 8F 58 9A 37 5F EB 73 1F C4 AB 22 5C 11 84 8C F8 9E 29 1F B2 71 33 97 0C 06 36 18 47 Î*Kä.Xš7_ës.Ä«".„Œøž).²q3—…6.G
00000140 4A 89 28 01 ED D6 8F 54 69 8C 5E 5B 50 67 46 F6 76 5A 6F 7F 12 25 DE A4 DA 11 40 FE B6 0F 65 07 J‰(.íÖ.TiŒ^[PgFövZo…%Þ¤Ú.@þ¶.e.
00000160 45 24 1C 69 36 95 88 3D CB 21 E6 FB FE FB B8 5A 29 91 94 80 36 A5 2B 5D E$.i6•ˆ=Ë!æûþû¸Z)‘”€6¥+]
[/code]
But then again, 0418_ does outright say that he believes it’s 256-bit encryption, “probably of the AES or Rijndael cipher algorithm”. However, AES is equivalent to Rijndael-128 (128 bit block size) with a key size of 128, 192 or 256 bits. If the block size is 256 bits, then we’re left with Rijndael-256.
EDIT:
I think it says “147Pm”, which is an isotope of Promethium. The scribble on the right looks like a small curved arrow pointing down at “2-8-18-23-8-2”, which is the electron shell structure of Promethium.
I can’t get OpenSSL to work with Rijndael, so no prowress on my part. The only implementation I found was .NET, this one
But I don’t trust myself to make it work with warranties that it’s decoding as it is supossed to be. I’ll try to find something that it’s already built and with an option to use a block size of 256 bits. Maybe a cryptopp library for the C++11 code made by pointless.
About the modes I’m not sure, I really like the theory about [ABORTIVE.] instead of [TERMINAL.] meaning abort Initializatioin Vector and therefore use ECB mode. Any ideas about the digest for the password? It seems we’re finally getting somewhere with the puzzle, or at least narrowing it down.