I have nothing conclusive yet.
I've been archiving WL data for years now, fully expecting the attacks on their staff and infrastructure but I've been impressed with how resilient they've been so far.
If you'd like to download the wikileaks archives yourself these are links you need.
Warning: This is not something to take lightly, and you should be aware of any potential legal consequences for both downloading and holding these materials in your country. These archives can be massive files, and whatever outbound IP address you use to get them will undoubtedly get logged somewhere .. But you know what they say:
Main site archives and torrents
This massive torrent contains all past releases and files (Except the podesta leaks)
https://file.wikileaks.org/files-all.torrent
You can browse the archive directly (while it lasts) here:
https://file.wikileaks.org/file/
Clinton / Podesta Email leaks
These aren't available as a package yet, but the wikileaks site can be scraped with curl:
To download all emails so far
curl https://wikileaks.org/podesta-emails//get/\[1-31817\] -o "#1.eml"
To download specific batches of emails just modify the curl command like this, for example this would download just batch 18 (30483-31817)
curl https://wikileaks.org/podesta-emails//get/\[30483-31817\] -o "#1.eml"
The batches of emails released so far :
1-2080 first batch (07/10/16)
2081-4160 second batch (10/10/16)
4161-5360 third batch (11/10/16)
5361-6568 fourth batch (12/10/16)
6569-7241 fifth batch (12/10/16)
7242-9077 sixth batch (13/10/16)
9078-10249 seventh batch (14/10/16)
10250-11107 eighth batch (15/10/16)
11108-12173 ninth batch (16/10/16)
12174-15386 tenth batch (17/10/16)
15387-17281 eleventh batch (18/10/16)
17298-19115 twelfth batch (19/10/16)
19116-23608 thirteenth batch (20/10/16)
23609-25204 fourteenth batch (21/10/16)
25205-26304 fifteenth batch (22/10/16)
26305-27024 sixteenth batch (23/10/16)
27025-30482 seventeenth batch(24/10/16)
30483-31817 eighteenth batch (25/10/16)
Insurance Files
"In case of emergency" , the contents of these archives are currently unknown. Many people are working on unlocking these files, they are bound to contain some juicy stuff ;)
https://file.wikileaks.org/torrent/2016-06-03_insurance.aes256.torrent
https://file.wikileaks.org/torrent/wikileaks-insurance-20120222.tar.bz2.aes.torrent
https://file.wikileaks.org/torrent/wlinsurance-20130815-A.aes256.torrent
https://file.wikileaks.org/torrent/wlinsurance-20130815-B.aes256.torrent
https://file.wikileaks.org/torrent/wlinsurance-20130815-C.aes256.torrent
https://archive.org/download/wlinsurance/wlinsurance_archive.torrent
https://archive.org/download/wlinsurance
Cryptic Tweets and potential key clues
pre-commitment 1: John Kerry 4bb96075acadc3d80b5ac872874c3037a386f4f595fe99e687439aabd0219809
pre-commitment 2: Ecuador eae5c9b064ed649ba468f0800abf8b56ae5cfe355b93b1ce90a1b92a48a9ab72
pre-commitment 3: UK FCO f33a6de5c627e3270ed3e02f62cd0c857467a780cf6123d2172d80d
eta numeris 392D8A3EEA2527D6AD8B1EBBAB6AD
sin topper D6C4C5CC97F9CB8849D9914E516F9
project runway 847D8D6EA4EDD8583D4A7DC3DEEAE
7FG final request 831CF9C1C534ECDAE63E2C8783EB9
fall of cassandra 2B6DAE482AEDE5BAC99B7D47ABDB3
Insurance File 1 Partial Decrypt
This was the first insurance file distributed by wikileaks back in 2010 :
This file can be partially decrypted - take one layer of the onion off with this command
openssl enc -d -aes-256-cbc -in insurance.aes256 -out insurance -k "ONION"
At this stage, its just binary data with no file header so I assume this is another layer of encryption - hopefully we can get more crypto geniuses on this problem because at this stage its unknown if the normal dead-mans switch procedure has been interrupted or not.
Lets crack these files!
Where is Assange ?
It's getting harder to find reliable wikileaks news updates amongst the noise and rumor.
The wikileaks subreddit is being heavily censored by a heap of new moderators
People are being banned from twitter and/or blocked by the wikileaks twitter account for asking for PGP verification.
One good subreddit that's active now is /r/whereisassange , and there are more up to date resources and twitter hashtags being organized there as well as a chat server.
I will post more information about why I believe JA has been killed once I have something conclusive - they still haven't followed through on their own twitter poll asking how they should prove it.
This whole situation sucks, I really hope I'm wrong and we're not adding Julian to this list of wikileaks deaths for this year alone:
I'll update when I have something solid - stay safe people.
~Psst - lets connect on twitter!