It’s no use because logon server’s IP is obviously fictional. I’ve tried to use it as proxy without any luck. However, phrase “this location” looks interesting. Maybe we should try to use IPs of places near Black Mesa.
i have found code at bmrf.us/img/EAS_bg.jpg it has a lot of characters so i made txt here -->https://drive.google.com/file/d/0B0yI-egbonEeVVB1YlhKTEFnSVE/view?usp=sharing
How did you uncover this? Please explain your methodology.
Never mind, I found it. I would suggest altering your GoogleDoc to reflect the color coding, as everything is important.
I looked at the code but I still don’t know what I’m supposed to look for…
Maybe proxying a New Mexico IP? I think BMRF was in New Mexico.
Is that the code of the image from the EAS? If it is then it has nothing inside, the checksum is the same as the image found in google where they took it.
I’m a bad at this so im not really sure how to do that sorry but found in inspect element
i think its unicode
Where did you find this?
Edit: Ok, for people looking, go into https://bmrf.us/img/EAS_bg.jpg , go into the img folder and click EAS_bg.jpg and look at the code
“2. Halos is definitely encrypted (and can be decrypted), but NOT with openssl tools.” - Stormseeker
Would that effectively remove any suspected ciphers listed at https://www.openssl.org/docs/apps/ciphers.html#cipher_strings? If so, it would remove some dead ends…
found something on storm seekers website i dont know if its arg related use google inspect elementvar code = [], lulz = “38,38,40,40,37,39,37,39,66,65”; go to fram then scripts
We can’t really know for sure. All he said was that OpenSSL was not the right direction. It is possible that he was referring to the way we have been using OpenSSL in the scripts that have been posted online (by inputting passwords with the -pass option). It doesn’t necessarily rule out all the ciphers that are implemented in OpenSSL. Other tools can produce a different result even if we are using the same cipher/mode and password (because the actual encryption key used may be different, or the output is formatted in a different way).
That’s the Konami Code, it was used to access an earlier part of the ARG
When looking at the Preview screen, do you see this:
https://drive.google.com/file/d/0B0y…hKTEFnSVE/view
or this:https://docs.google.com/document/d/1…it?usp=sharing
That is by no means the entirety of the characters, as they equate to roughly 50 pages. The patterns of the text towards the bottom reminds me of a couple of the Kyptos panels; specifically 2 and 4.
Kryptos 2
ABCDEFGHIJKLMNOPQRSTUVWXYZABCD
AKRYPTOSABCDEFGHIJLMNQUVWXZKRYP
BRYPTOSABCDEFGHIJLMNQUVWXZKRYPT
CYPTOSABCDEFGHIJLMNQUVWXZKRYPTO
DPTOSABCDEFGHIJLMNQUVWXZKRYPTOS
ETOSABCDEFGHIJLMNQUVWXZKRYPTOSA
FOSABCDEFGHIJLMNQUVWXZKRYPTOSAB
GSABCDEFGHIJLMNQUVWXZKRYPTOSABC
HABCDEFGHIJLMNQUVWXZKRYPTOSABCD
IBCDEFGHIJLMNQUVWXZKRYPTOSABCDE
JCDEFGHIJLMNQUVWXZKRYPTOSABCDEF
KDEFGHIJLMNQUVWXZKRYPTOSABCDEFG
LEFGHIJLMNQUVWXZKRYPTOSABCDEFGH
MFGHIJLMNQUVWXZKRYPTOSABCDEFGHI
Kryptos 4
NGHIJLMNQUVWXZKRYPTOSABCDEFGHIJL
OHIJLMNQUVWXZKRYPTOSABCDEFGHIJL
PIJLMNQUVWXZKRYPTOSABCDEFGHIJLM
QJLMNQUVWXZKRYPTOSABCDEFGHIJLMN
RLMNQUVWXZKRYPTOSABCDEFGHIJLMNQ
SMNQUVWXZKRYPTOSABCDEFGHIJLMNQU
TNQUVWXZKRYPTOSABCDEFGHIJLMNQUV
UQUVWXZKRYPTOSABCDEFGHIJLMNQUVW
VUVWXZKRYPTOSABCDEFGHIJLMNQUVWX
WVWXZKRYPTOSABCDEFGHIJLMNQUVWXZ
XWXZKRYPTOSABCDEFGHIJLMNQUVWXZK
YXZKRYPTOSABCDEFGHIJLMNQUVWXZKR
ZZKRYPTOSABCDEFGHIJLMNQUVWXZKRY
ABCDEFGHIJKLMNOPQRSTUVWXYZABCD
Here are the final four pages of the EAS text:
https://docs.google.com/document/d/1…DeBvspbps/edit
That’s not a public file
Try it now:
https://docs.google.com/document/d/1gqVTdDZRsa65mxv58tLWVuqMFX4842lLQfDeBvspbps/edit?usp=sharing
Maybe I’m just asking a stupid question, but I still can’t find this supposed code. I go to bmrf.us/img, click EAS_BG.jpg, and all I get is the image. Am I missing something?
Right Click, Inspect Element, and then click on the name of the image in there
It’s the binary data of the image, download it, open it with an hex editor, and there you go. But somebody a couple of pages back has already determined that the image was taken from google and the checksum is the same, therefore it has not been modified.
Dammit I thought we were onto something.