POSSIBLE ARG LARP ENCRYPTED THREAD (#7?)

Attached: pm ss.jpg (2390x4250, 1.01M)

ARGs are a waste of time

Attached: pm ss3 full.png (2383x3264, 3.7M)

Attached: dead.jpg (1710x7170, 2.12M)

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

Attached: claudia.jpg (1288x794, 166.69K)

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.

Attached: claudia2.jpg (1325x842, 132.96K)

forgot to say part 2/3 in last post

this is part 3/3

Attached: claudia3.jpg (1326x813, 206.85K)

>Reposting from the previous thread

Yeah, we're missing something.

Here's some Python code that should decrypt it, with output included:

pastebin.com/W2DLsYJ0 (embed)

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

Attached: sega.png (883x877, 140.74K)

Bump

archive for the thread: archive.4plebs.org/pol/thread/250954103/

I think I got everything important. If I can get a single user interested and save the images in the thread then I did my job.

I think you need more bumps.

Attached: Bumper.jpg (1000x504, 38.42K)

I don't understand any of this crap really, but it sounds like you may being doing God's work, user.

Qwixx is a great Family game
.
So the pic the public number (white dice) is a 3. Everyone can play the 3. The roller gets to play the private number as well. His options are:
1. Play the public 3 on red and the private 2 on yellow.
2. Play the public 3 on red and the private 4 on red. (red 2 + white 2)
3. Play the private 2 on yellow (yellow 1 + white 1)
4. Play the public 3 on red and private 3 on yellow.

dumb options:
5. play public on blue or green and private 4 or 3 on green or blue.
6. Take a forfeit.

The game ends whenever 2 colors get locked (5 x's on red and red 12 locked worth 2 x's) or a player takes 4 forfeits.

youtube.com/watch?v=ZAspNiPAUEE [Open]

Play on Tabletop simulator discord

Attached: B348353D-6A69-426B-B2B9-FE2787EDDB50.jpg (1024x965, 139.72K)

So right now we have two leads, and any Yas Forums anons with a sega cd rom emulator can follow the directions in the OP and get a final.bin file and run the file in the emulator.

thanks.

Attached: 1585446699400.png (16x16, 250)

Hi, M. How's the family?

I barely understand it at this point, the encryption anyway. Thats for anons way smarter than me. All I can tell you is the run down on why this is important.

Sources close to Assange say in late 2016 he was compromised, most likely killed, and the wikileaks twitter posted his dead man switch file. a 88 gig dump that supposedly contains enough dirt on every single thing the world governments have been doing wrong for years. we're talking shit that would get them hunted down and killed by their own people. and show some of the file names contained in the dump, notably "EUROPEANUNION, EUROPEANUNION2, ISRAEL_ISIS, NINEONEONE, and USHOMEDEFSOC_KILL_LISTS"

I'm sure you understand why its so important that we find the encrypted keys to that file.

Have a bump

Back to the top you gooooooo!

Attached: 1585454881614.png (2346x1198, 3.25M)

Bump

Im glad you anons are bumping because I'm realizing I'm forgetting shit

This is part 2 to this image
it also is a rundown of what exactly happened behind the scenes the days leading up to the deadmans switch file drop (that we know of)

Back everything up. Put it on archive.org. Spread the word. Get it solved.

either I'm being glowed on or I'm retarded and forgot to post image, probably the latter

Attached: leak2.png (1876x781, 131.9K)

also this is the tweet in question. with the torrent link to the original 88 gig file, that no one has been able to crack and live long enough to spread its contents

twitter.com/wikileaks/status/810813937566543872?lang=en

Bump

>imagine sitting home on a Sunday night staring at random numbers thinking you discovered some plot to take over the world

here is the EXIF data from the original image and thread in OP

time zone is GMT

Attached: exif.png (976x784, 83.42K)

I've been working really hard on the decryption but can't get anywhere. I'm not really sure if there is anything in there that would be worth all this effort. Plus I'm getting so sleepy, just look at the clock it is time for bed.

this is claudias directions to find the key using python and the blockchain, in pastebin form.

pastebin.com/Zv93KpQk

Bumparino

What is this brahs, i wanna get woke

...Huh? I'm totally lost

This is gonna be a long dump, this is a DETAILED timeline to catch newfags and zoomers up to speed

--SUMMARY-- (Detailed timeline with sources listed after this summary)
Apr 16: John Jones QC, Assange's U.N. Lawyer dies jumping in front of a train.
May 11: Michael Ratner, WikiLeaks' chief counsel, dies of cancer.
Jul 10: Seth Rich, DNC staffer who supposedly leaked DNC documents to Wikileaks, is shot in the back and dies. Nothing is stolen from his body.
Aug 5: Edward Snowden (source of leaks on surveillance by the NSA) tweets 64 bit code (potential dead man's switch)
It took 10 days before Snowden left another Tweet
Aug 10: Wikileaks offers $20k reward for information on murder of Seth Rich.
Oct 7: Podestamails leaks, first batch.
Oct 14: John Podesta tweets "I bet the lobster risotto is better than the food at the Ecuadorian Embassy”.
Oct 15: Joe Biden threatens Russia and blames them for Wikileaks – (Arrogant and open hostility)
Oct 16th/17: John Kerry visits the UK, personally pressures Equador to stop Assange from publishing documents about Clinton.
Oct 16/17: Wikileaks tweets SHA-256 prerelease keys.
Oct 16/17: Equadorian Embassy cuts off Assange's internet access.
Oct 17: Wikileaks Volunteer tweets that Julian is ok… tweet is now deleted.

cont.

Oct 17: Embassy tells a caller they can’t comment on Assange being alive:
youtu.be/536IK7YhsGw
youtu.be/A_jhLcvoZqc
At the exact same time this was taking place, Manning had a group of guys try to break her out prison. Read her statement and see how the dates and times match:
documentcloud.org/documents/3213878-Binder2.html
archive.is/87WS5
Oct 18: Pamela Anderson visits Assange. Feeds him a vegan sandwich apparently???
Oct 18: Witnesses photograph and report heavily armed police and vans outside Ecuadorian Embassy, are barred from approaching and have cellphones confiscated. Live feeds are cut off.
Oct 18: Fox News reports Assange will be arrested in a matter of hours.
Oct 18: file.wikileaks.org/file made publicly visible, file dates/timestamps changed to 1984 (Orwell reference).
The message 'The Insurance files may have just been released' is shown for about an hour: i.imgur.com/6IMYfUK.png
archive.is/UTGVq

cont.

Oct 20: /r/wikileaks, /r/dncleaks, /r/wikileakstaskforce and /r/nsaleaks add 21 new moderators and remove previous mods, all threads about Assange going missing deleted since.
Oct 20/21: Wikileaks tweets 5 tweets with misspelled words. The incorrect letters spell "HELP HIM". The Wikileaks twitter has never made a spelling error, let alone 5 in two days.
Oct 21: Massive DDoS attack on US internet. Wikileaks tweets to imply the attack originates from its supporters, asking them to stop, no evidence supports claim.
Oct 21: DDoS attack takes down Twitter.
At this point user notices that the insurance keys were posted on several sites and deleted. People start trying to post the information but it is immediately deleted. Everyone takes refuge in onion threads that also disappear.
Oct 21: London Airport evacuated due to "chemical attack", potentially used as cover to fly Assange out of country. (Conjecture but suspicious timing all the same)
Oct 22: Gavin MacFadyen (mentor to Assange and key player in Wikileaks) dies of lung cancer.

cont.

4TH PERSON RELATED TO WIKILEAKS NOW DEAD IN AS MANY MONTHS!!! MASSIVE RED FLAG!!!
Oct 23: Wikileaks Tweets poll asking how best to prove Assange is alive (he still hasn't appeared on video or at the window since).
Oct 24: Wikileaks Tweets video of Assange and Michael Moore recorded in June.
Oct 24: user is able to find the deleted keys. They are posted and deleted again.
Oct 25: Someone comes into a thread and gives user a hint about messages in the blockchain.
Oct 26: Yas Forums users successfully decode their first message in Wikileak's blockchain. Threads are instantly flooded by shills saying that it's not worth looking into. The blockchain is blocked with fees and 43000 unconfirmed transactions appear in the mempool.
Oct 27 (AM): user moves into an onion thread, posts code and a tutorial on decoding messages in the blockchain. Several files and messages are found.
Bitcoin 0.13.1 is released and a 'soft fork' begins:
bitcoin.org/en/release/v0.13.1
The blockchain is attacked: reddit.com/…/is_there_some_attack_going_whats_…/
Oct 27(PM): Several user report losing their connection. Talk of v&s and black bagging begins. Someone posts that they discovered a flaw that allows anyone to retrieve the password from the files. Clues are dumped and the onion threads go silent. On Tox chat someone says someone unlocked some of the files, warns that FBI will announce that new evidence was found in someone's computer and that a giant human trafficking operation would be exposed.
sli.mg/3srnQ3 - BASIC BLOCKCHAIN EXPLANATION

cont. fin

Oct 28: FBI announces they discovered new evidence on Anthony Weiner's computer:
Oct 30: FBI begins posting their own leaks:
twitter.com/FBIRecordsVault
(Said Twitter been almost completely dead until now)
Oct 31 – Nov 2: user begins analyzing strange code words like 'pizza'. Multiple connections are made.
Nov 3: Wikileaks confirms the validity of the information found:
twitter.com/wikileaks/status/794247777756860417
Nov 5: Manning's statement [referenced Oct 17th] is released: documentcloud.org/documents/3213878-Binder2.html
Nov 6: Huge DDoS takes down Wikileaks for first time in years.
Nov 7: Various entities notice hundreds of Podesta and DNC emails are missing from recent leaks, accessed with direct entry.
Nov 8 (AM): New insurance files are posted: twitter.com/wikileaks/status/796085225394536448
Nov 8 (PM): Trump wins.
Nov 8(AM-PM): Large numbers of cyber attacks target Saudi Arabia and Emirates: i.sli.mg/dGc3TG.png
Nov 9: A single file is changed on the file.wikileaks.org/torrent
Nov 10: Staff publicly states their concern for Assange's continue silence after the election. Incorrectly states that insurance files are future leaks and refers to the ones posted on Nov 8. These are the first files to have filenames that reference their content: reddit.com/r/IAmA/comments/5c8u9l/we_are_the_wikileaks_staff_despite_our_editor/

I should add this entire chain of events took place in 2016

based and historian pilled. Should be updated with years at this point though 2016, right?

Attached: wikileaks kill.png (1088x744, 369.93K)

yeah, this is an old summary from an archived facebook post linking to an imgur album that links to a pastebin. its years old but lots of newbies came to Yas Forums in 2016 so if they've been paying attention they know the rest of the story leading up until now, or at least the important parts

Attached: psyops.jpg (599x627, 76.39K)

Bump.

part 1/2

Attached: 1.png (642x516, 389.19K)

part 2/2

Attached: 2.png (392x842, 366.4K)

bumb god speed anons

last thing I'm posting before I'm archiving and lurking the thread. I wanted to get all of this info into one thread for linking purposes. Thanks all for the bumps.

Attached: key bin.png (1902x3184, 1.04M)

Guys. I was just going on a hunch. It could literally be anything, no code has worked. At a time like this, Wikileaks would drop this on Twitter wouldn't they? Godspeed regardless.

Attached: 12.png (492x29, 1.61K)

good work user - somebody suggested a public google dox acc we can all file dump into

If the code were dropped on Twitter the entire internet would be nuked. Makes the whole “10 days of darkness” Q talks about seem actually possible. Kill Assange if he is still alive, send out the deadman switch, have people be prosecuted with the leaks.

- 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)

somebody in thread #5 last night had a really good copy of the original image

>POSSIBLE

Attached: ohDKCIOg.jpg (728x574, 29.14K)

I've been trying to upload the image, I keep getting "connection error" every time, I think we're being glowed on. Maybe taking the imagine and changing the name, converting it from png to jpg or vice versa, and resizing it could work.

change the file name

hoping this works, this is the enlarged version of the original

Attached: big_key.png (544x548, 18.42K)

Thanks for this, gonna mess with it tomorrow.

People think the wikileaks twitter and website have been compromised, or now under the supervision of a certain 3 letter agency.

Like claudia said the chat logs above. Julian was compromised.

Seems we need more attention.

Attached: 1585454021743.png (577x579, 5.38K)

Yes. I think WL has been compromised, however if somehow the key were to be leaked on Twitter by some other people who somehow got it from the blockchain or whatever

we did it!!!
have a bump