Wikileaks Sidesteps Publishing Public PGP Key
An anonymous reader writes "Repeated requests toward the Wikileaks staff regarding their use of PGP have gone unanswered. The current public PGP key posted has been expired since November 2nd, 2007. A response on their PGP talk page notes that the 'SSL based mail submission system' will be the secure online method of document submission. At the current time, there is no method to safely encrypt any postal communications with Wikileaks or verify that any given communication actually originated from a Wikileaks staff member."
Doubtless there are some complicating factors here -- but what is the best way to keep a confidentiality-centric site like Wikileaks trustworthy?
A decade ago, every geek had a PGP key, keysigning parties were a great way to spend a Friday night, and everyone was raving about Schneier's eggheaded but useful tome Applied Cryptography . Now when I ask otherwise normal geeks if they have a PGP key, they just look at me like I'm from Mars. I don't understand, PGP has gotten only easier to use, there's a great Firefox extension for it, but it has faded in popularity.
Unfortunately, there isn't - information is only as trustworthy as the source.
Once documents have been leaked, organizations know they can't put the cat back in the bag but they want to close the bag to prevent further escapes. Sure they sue but they sue to get the names of submitters (i.e. Apple vs. Think Secret, or Craig what's his name at Microsoft threatening to find the leaker of the Halloween documents via secret Exchange magic)
Wikileaks appears to want to provide a way for submitters to deny they even submitted anything to Wikileaks. Sending an e-mail to wikileaks with the contents encrypted is a clear indication that you're sending something to them. By the time the leaks are made public all they want to do is find the person, searching for something that sent pgp encrypted mail, even without being able to decrypt the actual contents, is going to be good enough for them.
An ssl page, especially if wikileaks sets up some sort of drop system with other domains so you aren't obviously submitting to wikileaks, is much harder to track because people use ssl pages all over the internet all the time. If PGP were used more frequently then they could probably use that with a drop system as well, but it's just too rarely used.
It makes sense, really. Anything you send to WikiLeaks you intend to be told to everyone.
I think what they mean by "provides proof of intention to conceal" is that they don't want people leaking something and then saying "aha! You just told everyone something that I meant to be kept private, I'm going to sue! Why would I have encrypted it if I had meant you to release it?"
And that person would have a point. It's hard to think how someone could post something to WikiLeaks, so that it can be publicly posted, but desire that their information be transmitted encrypted. The assumption should always be anything you send to WikiLeaks is public, and allowing encrypted submissions may make this unclear.
If they need to submit the information anonymously they should do it anonymously, PGP can't help with that.
// MD_Update(&m,buf,j);
"Proof of intention to conceal" would refer to the fact that when the next scandal at ACME is published, and only one of their faithful employees ever used PGP as evidenced by their router logs, that would constitute enough proof to sue, even without being able to read the actual contents of the mail.
So what the nice folks at wikileaks are saying is that you might as well ditch PGP and use web-based SSL forms so you can just claim you were paying your annual Playboy magazine subscription, or whatever. Or you could send all your mail with PGP and try to convince everybody else to do so as well.
So yes, PGP isn't going to do you much good, but not for the reasons you stated.
I think you're misunderstanding them.
I read it as "the Chinese or other totalitarian governments might punish you solely for using PGP".
The gmail revenue stream depends on targeted advertising, which means they need to have a daemon read your mail. If they supported encryption as standard, they'd be cutting off some not-insignificant portion of that revenue ; regardless of how much they'd like to support the feature, their responsibilities are to their shareholders ; unless they can find a way of making equivalent or greater revenue from encrypted mail, they can't field it as a feature.
I can't envisage an encrypted mail service that has an externalized revenue source, so the only way to fund it is by the customer paying. Which then begs the question, who do you trust enough to pay them to keep your secrets safe? In my case, I no secrets worth keeping, but if I did, I wouldn't trust anyone else to keep them for me.
Open-source, peer-reviewed encryption, under my own control, is the only technique I would trust to keep digital secrets transmitted across a wire.
The best kept secrets are of course the ones you keep solely in your own head.
There isn't. By verifying that anyone is anyone the cover is blown. Regardless the best use of it is still to post anonymously and link as many people as humanly possible. Then even if your cover is blown, the message still gets out. If you're a whistleblower, this is something you should have accepted long before you blew the whistle
Indeed - or a UK member of staff has been forced to turn the old key over under the terms of RIPA, and Wikileaks are interpreting RIPA's provisions in such a way as to be sure to keep that staff member out of prison.
Well, since people can't use PGP with their regular email addresses anymore to correspond with wikileaks, what's stopping them from making a dummy gmail account or something? It takes all of a couple seconds and that way you don't even have your regular email address associated with them at all.
Weaksauce as they say...
I'm in a situation where I need to *prove* that someone has opened/read an email. I know there are paid "registered email" services, but they seem a bit overkill to me. And return receipts are jokes, since they aren't widely supported.
The short answer is "don't try to make SMTP do something that it wasn't designed to do".
The long answer - send people unique links to a web server that you control.
Wolde you bothe eate your cake, and have your cake?
That's silly, you don't have to distribute the private key, that's the whole point.
Take the wikileak's SSL key. How do you know that's their private key and it's not a MiM attack? You know that because verisign (or someone) signed the public key. They did that with a private key -- and wikileak doesn't have it!! Oh nos!!!
There's always a private key you don't have. That's the whole point of asymetric cryptography. PGP is no different.
So this argument is all very silly.
Imagine if you weren't allowed to use roads because a bus company complained about your driving 3 times. --skunkpussy