LaCroix wrote:Also, given the fact that he probably hasn't used an off the shelf system, but multiple self-written encrypters in layers (I would have done if I were him.) So they can't just bully software companies into giving them the used algorithm (in secret, of course), which is needed if you want to break a code of modern complexity.
Doubtful, homegrown solutions have the problem that you have only limited resources to test their viability and security, which will result in exploitable flaws in the algorithm and/or implementation errors in the cypher application.
Also, if you made your own algorithm and wrote your own cypher app, you have to distribute your own application so people could decrypt it too. At that point you can be sure, that fuckton of government hackers, security freaks and other bithunters will pore over your released app with a fine comb to see how it works and whether it'll contain exploitable bugs(it'll unless you had a army of programmers and testers to test the fuck out of it). It's not easy, can be made difficult with programming tricks, but it can be done.
Meanwhile, tried and tested algorithms implemented in tried and tested crypto libraries and apps already used widely. Especially if they are open source apps, hosted on servers not under US jurisdiction. You can be sure that people went through the code of OpenSSL, GnuTLS or GnuPG many times to make sure they are as secure, error and backdoor free as it's possible(and found
more than a
few vulnerabilities, even if some of them are theoretical)
Encrypting the content multiple times, with multiple strong cyphers (with no known vulnerabilities) is still a more viable solution, because even if the outside encryption is brute forced, now you have to start the whole cracking process again, with a different cypher...
But even IF they manage to crack the code - what will they do? It's not as if that file isn't distributed to all over the planet. Knowing what's in it won't help them one bit if it's really a bombshell. And I doubt that this is just a bluff, I predict that they have put all the documents that would create havoc in there - those they couldn't leak because of their volatile content.
They can still check whether it's content is credible threat and start damage control or it's something only the WikiLeaks people thought as damning evidence but in reality it's harmless.