I tried to ask Sup Forums but they're fucking retarded and don't know anything about cryptography
Julian Assange tweeted out this cryptic sequence earlier:
4767 5774 6a7a 4d6c 6330 666b 314a 3453 0000 0907 84b4 f787 7616 86f7 a737 5707 5736
It's 16 bytes followed by two 0 bytes followed by 16 more bytes, for a total of 34 bytes. So it's basically two 16 byte numbers. I don't know what they are, but whatever they are, it's highly unlikely that they're a sort of hash or some other kind of "random" number.
My reasoning is, every byte in the first 16-byte number starts with a 0, and every byte in the second 16-byte number ends with a 0. The chances of that specifically happening with 2 random numbers is 1 in 4.3 billion, or 1 in 1.1 billion if you control for similarly strange scenarios happening, e.g. both 16-byte numbers having bytes all starting in 0, etc.
Anyone know what this is?
I tried to ask Sup Forums but they're fucking retarded and don't know anything about cryptography
Other urls found in this thread:
twitter.com
w.net
w.net
twitter.com
twitter.com
twitter.com
file.wikileaks.org
file.wikileaks.org
file.wikileaks.org
cmgds.marine.usgs.gov
m.forocoches.com
pastebin.com
youtube.com
pastebin.com
twitter.com
>asking Sup Forums
Won't make that mistake again. I only asked because I googled the ASCII conversion of the first 16 bytes and saw a thread on Sup Forums. They're fucking retarded.
Here's the tweet btw
twitter.com
>append it to tinyurl.com "SOMETHING"
its actually a link to either a URL that is 8192 bytes long, or it is some sort of block chain message.
A block chain message contains a link to the next block, and a payload
I think it is a blockchain message because I keep repeating the "extract 16 bytes" and append a tinyurl address, and I get another 8192 bytes block
This is interesting...
I'm not sure what you mean. I feel like it might be a code. Mostly because if you reverse the second 16-byte number, every byte is one of the 128 main ASCII characters, although two are the DEL character.
Ignore the rest of the data, only the first 16 bytes are relevant
tinyurl dot com slash GgWtjzMlc0fk1J4S
He is doing a blockchain data message
Friendly reminder the last hashes "Assange" tweeted out DID NOT MATCH the insurance files that were subsequently posted later. You can all easily verify this for yourselves.
Stay frosty, anons.
you will get an address to w.net
ignore w.net
the rest of the url is actually a Base64 coded block
Transform it to binary, and you will get another 16bytes long pointer to the next block
Oh I'm an idiot, that page didn't load, I didnt even look at the URL, nice
...
Has anyone recited the numbers into Alexa?
I think I should make a discorddapp group in order to share my findings with people who might actually be interested in this sort of things
I have recovered 40 blocks of binary data, using the "blockchain" message algorithm
But to be honest, i think Sup Forums is nothing but a bunch of larpers, and that I should probably keep my findings to myself
have a good evening
Sup Forums - Chinese phone and tablet discussion
:( I'm not a larper, I'm just an idiot. Can you at least tell me what you did with that long URL? I know what the blockchain is, is that base64 number the data of a whole blockchain block?
>what you did with that long URL
convert it from base64 to binary
>is that base64 number the data of a whole blockchain block?
is the whole "block"
once the block is in binary form, you can take 16 bytes from it, convert it to ascii, and get the link to the next block
Pasting my explanation from one of the threads that got slid:
These are almost certainly md5 hash signatures. You don't DO anything with them except save them for later. They're the end result of a one-way formula.
Here's one I generated from a file: f59f 6030 ac6c 5d6d 1037 896a 1906 f009
Here's another: a8fa c042 09d4 82e1 7ec4 609b b04b bc55
Now, if you can trust those signatures because you got them from my blue-checkmark Twitter account, later I can give out URLs/torrents for two files. After you download them, you run them through md5, and if you get the same hash signatures, you know they haven't been tampered with since I created the ones I gave you.
That's what it is. You can't "figure them out" or get any information about the original files from them. If he releases two files soon, you can use them to verify the files you got through an untrusted channel haven't been tampered with. If he doesn't, you have 64 useless bytes.
They're also not a "dead-man's switch." That's when you set something up so that if you don't keep it updated, it "fires" and sends something out. Like giving an envelope to a friend and telling him to mail it if you die. A programmer could have a job on his computer that checks the age of his web browser's history file, for instance, which is updated every time you click a link, and if that file gets more than a week old, send out some prepared emails. It'll never get that old with normal use, but it will if he dies or gets locked up, and it will "fire" on its own. That's a dead-man's switch.
Assange Decoded!
Message as follows:
gibberish
Can anyone comment on this? Is it true?
explain this
He's saying these hash signatures don't match those earlier Insurance files. I wouldn't expect them to, frankly. He probably put out signatures at the time, along with those files. These are likely to be for files which are forthcoming.
try it for yourself
twitter.com
>4bb96075acadc3d80b5ac872874c3037a386f4f595fe99e687439aabd0219809
twitter.com
>f33a6de5c627e3270ed3e02f62cd0c857467a780cf6123d2172d80d02a072f74
twitter.com
>eae5c9b064ed649ba468f0800abf8b56ae5cfe355b93b1ce90a
file.wikileaks.org
>sha256sum 2016-11-07_WL-Insurance_US.aes256 ab786b76a195cacde2d94506ca512ee950340f1404244312778144f67d4c8002
file.wikileaks.org
>sha256sum 2016-11-07_WL-Insurance_UK.aes256 655821253135f8eabff54ec62c7f243a27d1d0b7037dc210f59267c43279a340
file.wikileaks.org
>sha256sum 2016-11-07_WL-Insurance_EC.aes256 b231ccef70338a857e48984f0fd73ea920eff70ab6b593548b0adcbd1423b995
Mismatch.
There are hyphens and underscores in it though. So is it really base64?
thx good thinker
It is a url safe Base64
why is /g so fucking useless?
Because it is infested with "Microsoft Certified" meme guys
Install gentoo
dummy
fucked up the copy pastes and order
twitter.com
>4bb96075acadc3d80b5ac872874c3037a386f4f595fe99e687439aabd0219809
twitter.com
>eae5c9b064ed649ba468f0800abf8b56ae5cfe355b93b1ce90a1b92a48a9ab72
twitter.com
>f33a6de5c627e3270ed3e02f62cd0c857467a780cf6123d2172d80d02a072f74
if you search this it leads to the website below.
>GgWtjzMlc0fk1J4S ?v?7W?W6
I'm interested but this is way out of my normie element.
Godspeed.
Cross-poster from Sup Forums. I can confirm that Sup Forums is basically OS wars, Intel vs. Nvidia and basically consumer electronics.
Well I made sense of it finally but, do you only use tinyurl for the first block? I converted the URL safe base64 to binary and then to hex and the whole thing is gibberish, no long sequences of ASCII that I could plug into tinyurl
Goodbye CIA.
>every byte in the first 16-byte number starts with a 0 and every byte in the second 16-byte number ends with a 0
sounds like positive signed integers
Did anyone do this yet?
Mah nigga
I have, yeah. I'll make a pastebin
>The chances of that specifically happening with 2 random numbers is 1 in 4.3 billion
touch up on your math. There are 32 bytes in question, ignoring the two null bytes. 25 out of those 32 bytes start with zeroes.
How many ways are there to chose 25 out of a pool of 32? You need to use combinatorics, i.e. n-choose-r
32 choose 25 = 4.2535295865e+37
The first 16 ALL start with 0, the last 16 ALL end with 0. The chances of that is 1 in 4.3 billion. I took it down to 1.1 billion for reasons I explained in the OP.
CIA guy come baaack. Where are the 16 bytes that point to the next block? Do you have to mine it like a bitcoin block?
How do you figure 87, for instance, in the second batch of 16, ends with 0? In binary, that's 10000111.
Alright it's past 12 EST and nothing happened yet. I'm going to bed good night.
yawn, wake me up when something actually happens then
Feeling sleepy. This is a big nothing burger boys! lets get some rest.
It's 2pm you fucking degenerate.
Fuck. Okay, I fucked up in two ways.
I somehow confused it in my head and thought I could leave out the fact that I reversed the second 16 bytes before converting them to binary.
The second way I fucked up is that even when you do that, the very last byte starts with a 1.
Not that it matters now, the guy that posted in here about the tinyurl thing has it all figured out.
DONT YOU 404 ON ME!!
We need the CIA guy back, he's the only one who can save this thread.
that was awesome
I am sure Sean Hannity will answer all of your questions tomorrow. Go to sleep, user.
cmon you autistic fucks, someone figure out what to do with that block. isnt your autism kicking in right now? dont you want to find Hillary's emails and make her say ree?? arent you all good boys that want tendies? figure this out you gay little niggers
bump
Why the fuck isn't this shit higher than "What's your major pol"
Magic wormhole maybe?, Google its a python module
bump
It's Satoshi's private key you Bitcoin fags. Hehehehhe.
interesting timing with the ethereum fork
>16
>1+6 = 7
>7 + 16 =23
>23
We can get the message chain already but without any context behind the data contained in each block it's pretty meaningless for now.
If you all still don't believe it's a block chain and don't want to check the links for fear of getting party vanned, notice that the 17th byte is 0000. OPs rambling about bytes starting with 0 and whatnot are nonsense, this really is a hash.
i see what you did there kek
A byte has 8 bits dude, not 4. You mean the 17th and 18th bytes are 0000 in hex. And yeah what I was saying was definitely wrong about the last 16 bytes but it's still right about the first 16, they all start with 0 because it's not a hash, it's ASCII, because it's a tinyurl like that guy said.
I sitll haven't been able to find another tinyurl link in the block though.
btw here's the block converted to ASCII, there doesn't seem to be any long enough sequence of URL safe characters to use as a tinyurl
whoops I'm fucking gay
pastebin.com
I think the 0000 have to replaced with numbers he put in other tweets
Yeah my bad I meant two bytes.
>It's not a hash
It IS a hash. That latter half including the 0000 was a hash specifically computed to start with 0000. It was computed using the data in the message plus an arbitrary string. If the miner gets a hash starting with 0000, the arbitrary string is broadcast to all the other miners so they can verify that the winning miner got it right.
Basically we have:
[Next] 0000 [This]
Next is the pointer to the next block, the one in the tinyurl link.
This is the pointer to the current block. It may not have a meaningful message attached if it's the first block.
It's not rocket science to follow this block chain. Simply convert the first 16 bytes in the binary in the pastebin to ASCII and use a tinyurl again.
Explain why
I said the first 16 wasn't a hash. I still don't quite understand the last 16 being a hash if you include the 0000, because that would make it 18 bytes, not 16. But maybe the 16 without the 0000 is a hash?
As for using the first 16 bytes as a tinyurl, have you tried it? It doesn't work.
I'm getting sleepy
nice psyops
People shouldn't be running these hash with 0000
Remove zeros and it's perfect length for sha256 key . I was wrong in earlier post
Is it of note that he probably created a custom tinyurl for this? tinyurl doesn't seem to use capital letters in its urls unless you make the shortened part yourself
Holy shit we got trolled
tinyurl user made that tinyurl link, not Assange
fuck
Why would he use tinyurl for anything? That website is garbage.
This is an encryption key, whether or not if it actually contains some non-random parts, which you can't really prove it does.
He tweets out keys in case something goes south during the later publishing of encrypted info.
In the past he's labeled those things, see it's not a key, he gave us two 16 byte numbers, no encryption key is 16 bytes long
sounds like a textbook case of (pic related)
Without 0s I got this
...
3 hours.
Dude why would he just stick four 0s in there randomly though. That makes no sense. The 0 bytes are there to separate two things.
...
I'm thinking first 16 bytes are meant to be taken as 7-bit ASCII and the last are some sort of key. Who fucking knows, I'm too tired to think about it anymore.
Pic related
We are talking about Julian here
You have no idea what you are talking about. Julian posted:
>4767 5774 6a7a 4d6c 6330 666b 314a 3453 0000 0907 84b4 f787 7616 86f7 a737 5707 5736
That is 4x4x17=272 bits you fucking retard. Let me guess, you are a CS major.
Kys faggot.
calm down. you're right, I was wrong
I was thinking keys were on the order of 128/256 bytes, but I dont claim to know anything about cryptography
is there a precedence for him cryptically tweeting out encryption keys?
Kys faggot.
Do not attempt to create software. You will make humanity worse if you attempt to produce anything.
you sound really fucking displeased with your life, dude. I'm not even in school for programming, relax.
Yo, calm down Julian. We'll figure it out eventually give us some slack. Damn dude