9495c7c6e4b653e315d48f0f68fe700c5b97470e
9495c7c6e4b653e315d48f0f68fe700c5b97470e
Que será esto?
Que será esto?
*Is Abaddon to be feared?*
*Is Abaddon to be feared?* My argument is no. I'm interested in knowing the origin of the cited scripture. Or is it scripture? It looks like it may be another person's version of the scripture which comes across as... It feels evil and foreboding. I have 2 sources that paint a different picture. In biblical text the apostle John translated the Hebrew word Abaddon to Greek which is Apollyon. Apollyon means “Destroyer,” and is given as the name of “the angel of the abyss.” Though most reference works apply this name to some evil person or entity, the whole setting of the apocalyptic vision in Revelation is to the contrary. It consistently portrays angels being used by God to bring woe and destruction upon His enemies. Not the devil or his demons. Destruction is not always evil. The Interpreter’s Bible says: “Abaddon, however, is an angel not of Satan but of God, performing his work of destruction at God’s bidding.” It wasn't until the 19th century that the 'angel of the a...
Passcodes, or a code that leads to a passcode
ReplyDeleteShould be hexadecimal code....
ReplyDeleteIt looks like hex to me too. But converted to ASCII it is still meaningless to me
ReplyDeleteÇÆä¶SãÔhþp[G
I tried using a rot13 decryption on it, but that lead me deeper into the briar patch and no closer to a solution. Good luck?
Maybe in binary with a fixed length the ones will spell out plaintext? Not equipped for that manipulation on my iPad, and my computer recently died so in process of getting the next generation online.
ReplyDeleteDEC : 848270848141329065568252864380689750440591968014
ReplyDeleteHEX: 9495C7C6E4B653E315D48F0F68FE700C5B97470E
I got rubbish on ascci
ÇÆä¶SãÔhþp[G
Also got something. Can't make it out, I'm no programmer.
ReplyDeleteconst uint8_t data[] = {0x9495c7c6e4b653e315d48f0f68fe700c5b97470e};
Or transform an unsigned value into a signed one, or vice versa, for example:
ReplyDelete(uint8_t) -1 : convert the signed int “-1” to an unsigned byte (i.e. “255”)
So, it's a value converter from signed to unsigned digits..... might be as far as I can get, though.
Sergio Montserrat Thanks , really, thanks
ReplyDeleteWhere did you get this? Maybe it's a SHA1 hash result
ReplyDeleteWalter Yung It's weird, but I get to my mail, I was talking to some friends of Ingress and research ADA when, a few minutes (5) I get that key, I do not understand, and although it may be a mistake (which I has arrived), I think that not everything is what it seems
ReplyDeleteSergio Montserrat Are you sure about the DEC result? Looks awfully small for such a big HEX...
ReplyDeleteConny Pearce Sadly, not. I passed it through a converter and copied it straight from the result, but it could be truncated somewhere.
ReplyDeleteLooks to me that the delimiters have to be applied first:
ReplyDelete9495 c7c 6e4b653e315d48 f0f 68fe700c5b97470e
3e3 might be also something
Sergio Montserrat I checked that. It is correct, but I can make no sence of it...
ReplyDeleteDaniel Scherrer Why do you think these are delimiters? Because of the symetry?
Conny Pearce Yes, and the numbers in the delimiters might be needed to decode the parts separately. could also be totally wrong, checking some arranging things
ReplyDeleteIn tail there are e3e3.
ReplyDeleteHow you have obtained that? The mail maybe contain another tip
maybe it's better for you to download the source of the mail and share it here. it's possible that other clues are hidden in those non-visible parts (eg. html code) of the mail.
ReplyDelete