Okay anons, I think I’ve gotten the first layer off. Can’t really be sure, though—I’ve never had the faintest interest in cryptography.
Looking through Wikileak’s history of releasing insurance files, you see that there are multiple layers of encryption on each of the files. There was at least one I know of where the first level of encryption was taken off. I’m guessing that that’s what just happened here—but it doesn’t mean that we’ve got a bunch of dirty nasty secrets to dig through; it just means we’re a step closer when we’re not even sure how many steps there are. On a positive note, I think it’s much more than a coincidence that this is happening right now, of all times—so I would download these and have them on hand, because the whole key could be given out at any moment.
So here’s how you take that first step. Note pic related: these files aren't just aes encrypted—they're aes256cfb encrypted. So AES Crypt doesn’t work. You’ll need to install openssl. I’m working off of a Windows machine—I found this page helpful:
https://www.tbs-certificates.co.uk/FAQ/en/openssl-windows.html
You'll need to do part a) set up a configuration file, but you won't need to do part b) generate a private key. You should also note that most of this, after installing openssl, involves working from the command line.
Once you've installed openssl and set up your configuration file, you'll go to the directory where openssl is installed, then run it. You should get an indicator that shows it's working–it'll be a prompt that looks like this in the command window:
OpenSSL>
Once you have that, you'll enter the command shown in pic related, with some adjustments. You won't need the "openssl" part, and you won't need to enter "enc" like in pic related–that would just encrypt the file even further. The command you enter should look something like this:
OpenSSL>eas-256-cfb -in C:\Downloads\wlinsurance-20130815-A.aes256 –out C:\Downloads\wl-A -pass pass:Berlin?A!Collection+Of#Documents@Containing~Emails%FromUSA=A0F0
Let's break it down:
The first part "eas-256-cfb" tells OpenSSL what you're trying to do
The "-in" part is where you enter the path to the insurance file you've just downloaded. In this case, it would be on the C: drive, in the "Downloads" folder–yours may be different.
The "-out" part tells OpenSSL what you would like the output file to be named. This isn't like unzipping a file–we have no idea what we have on our hands here. In my case, I decided to output it as "wl-A". That’s just a file without a file extension at the end…which is appropriate because we have no idea what it really is. Just for reference, I added “.zip”, “.bz2”, and “.tar”, but no dice—it wasn’t recognized as any of those. I also tried opening it in gVim and notepad++, but even the smallest is far too large for those programs to deal with.
The "-pass" part is where you enter the password. In pic related, it's
>-pass file:wl-A.pass
That's because that anon wrote the password into a file he created named "wl-A.pass". It would be the smart thing to do if you were trying to keep your password private, but that's not the case here; you should just be able to enter the password as above rather than the way it was done in pic related.
Note: if you do decide to use a password file, you should put the full path. So let’s say you wanted to put that file in the same folder as your wlinsurance file—you would enter “-pass file:C:\Downloads\wl-A.pass”
Once that’s done, I guess you’re a step closer than everyone but the ones that figured this out, maybe some well-connected people, and Wikileaks.
Again, I'm no expert. Maybe I'm missing a post somewhere, but I haven't gotten any further, and I don't have the ability to tell if I've even made progress. I guess the fact that there was some output is a good sign, but tonight wasn't the night I got to see Merkel in her dad's Nazi outfit.