POSSIBLE ARG LARP ENCRYPTED THREAD (#7?)
ARGs are a waste of time
here is the claudia chat logs, supposedly she explains how to get ahold of a working key using bitcoins blockchain encryption and a python script.
part 1/3
after I'm done with the image dump relating too WikiLeaks and the key, I'll try and post discoveries anons made in the previous threads.
forgot to say part 2/3 in last post
this is part 3/3
>Reposting from the previous thread
Yeah, we're missing something.
Here's some Python code that should decrypt it, with output included:
pastebin.com
It is a valid decrypt, but the result is gibberish. Same if you try to reverse the byte order of the key, or reverse the bits per byte.
This is the bitstring I parsed from the image, and which several other people also got:
011000010010001110100101010011110101011100010000011101000110111000110110000011001000110101100100110001011100001010100110100010110001101101000110111011011100101101111011111010110101101011
1001101011111101011010100011100101100100110101111000110101110110011101
Someone else is calling this the inverted bitstring, but I think it's just the regular one. (Maybe they're confusing 0 RGB for white instead of black?) Either way, it doesn't work inverted or not inverted.
Possibilities:
- They just encrypted some random bytes to troll us and waste our time
- We're not getting the proper string of bits from the image, or not converting it to bytes properly
- We're not decoding the ciphertext properly (though I don't know how else you could; it's just plain base64, so it would mean they did some other thing which they didn't mention)
- The bytes look random because they're also encrypted, but with some other unknown key
Either way, not sure what progress can be made from here. You can try slicing and dicing the key bits some more, but I feel like that isn't the right path. I would expect the image to be read left-to-right row by row. But maybe it is supposed to be read vertically or some other way.
Beyond thinking of other ways to convert the image to bits, or encoding those to bytes (you'd expect it's just a sequential list of bytes, but who knows), don't know what else could be done. If another possible AES key turns up somewhere, you can try using that to decrypt the decrypted ciphertext here, I suppose.
this is as far as anyone got
this thread looks like its gonna 404, but I dumped what I could while I could. Hope it was of some use
-M
hope I can get this in before the 404