Washington Post Publishes… And Then Unpublishes… Opinion Piece By Ex-Intelligence Industry Brass, In Favor Of Strong Encryption
from the what-happened? dept
Update: And… the article has been republished at the Washington Post’s site with a note claiming that it was accidentally published without fully going through its editing process. Extra points if anyone can spot anything that’s changed…
Earlier this week, we noted with some surprise that both former DHS boss Michael Chertoff and former NSA/CIA boss Michael Hayden had come out against backdooring encryption, with both noting (rightly) that it would lead to more harm than good, no matter what FBI boss Jim Comey had to say. Chertoff’s spoken argument was particularly good, detailing all of the reasons why backdooring encryption is just a really bad idea. Last night, Chertoff, along with former NSA boss Mike McConnell and former deputy Defense Secretary William Lynn, published an opinion piece at the Washington Post, doubling down on why more encryption is a good thing and backdooring encryption is a bad thing.
Yes, the very same Washington Post that has flat out ignored all of the technical expertise on the subject and called for a “golden key” that would let the intelligence community into our communications. Not only that, but after being mocked all around for its original editorial on this piece, it came back and did it again.
Of course, you may note that I have not linked to this piece by Chertoff, McConnell and Lynn at the Washington Post… and that’s because it’s gone. If you go there now you get oddly forwarded to a 2013 story (as per the rerouted URL), with a 2010 dateline, claiming that “this file was inadvertently published.”
We recognize the importance our officials attach to being able to decrypt a coded communication under a warrant or similar legal authority. But the issue that has not been addressed is the competing priorities that support the companies? resistance to building in a back door or duplicated key for decryption. We believe that the greater public good is a secure communications infrastructure protected by ubiquitous encryption at the device, server and enterprise level without building in means for government monitoring.
First, such an encryption system would protect individual privacy and business information from exploitation at a much higher level than exists today. As a recent MIT paper explains, requiring duplicate keys introduces vulnerabilities in encryption that raise the risk of compromise and theft by bad actors. If third-party key holders have less than perfect security, they may be hacked and the duplicate key exposed. This is no theoretical possibility, as evidenced by major cyberintrusions into supposedly secure government databases and the successful compromise of security tokens held by the security firm RSA. Furthermore, requiring a duplicate key rules out security techniques, such as one-time-only private keys.
The op-ed also points out that “smart bad guys” will still figure out plenty of ways to use encryption anyway and all we’re really doing is weakening security for everyone else. And, of course, it raises the fact that if the US demands such access, so will China and other companies.
Strategically, the interests of U.S. businesses are essential to protecting U.S. national security interests. After all, political power and military power are derived from economic strength. If the United States is to maintain its global role and influence, protecting business interests from massive economic espionage is essential. And that imperative may outweigh the tactical benefit of making encrypted communications more easily accessible to Western authorities.
These are the same basic arguments that experts have been making for quite some time now. What’s also interesting is that the three former government officials also point out that the “threat” of “going dark” is totally overblown anyway. It raises the original crypto wars and the fight over the Clipper Chip, and notes that when that effort failed, “the sky did not fall, and we did not go dark and deaf.”
But the sky did not fall, and we did not go dark and deaf. Law enforcement and intelligence officials simply had to face a new future. As witnesses to that new future, we can attest that our security agencies were able to protect national security interests to an even greater extent in the ?90s and into the new century.
This is an important bit of input into this debate, and one hopes that the Washington Post only “unpublished” it because it forgot to correct some grammar or something along those lines. Hopefully it is republished soon — but even if it was published briefly, this kind of statement could be a necessary turning point, so that hopefully we can avoid having to waste any further effort on the wasteful idiocy of a second crypto war.
Filed Under: backdoors, encryption, going dark, james comey, jim comey, michael chertoff, michael mcconnell, mobile encryption, william lynn
Companies: washington post
Comments on “Washington Post Publishes… And Then Unpublishes… Opinion Piece By Ex-Intelligence Industry Brass, In Favor Of Strong Encryption”
This is not the article you are looking for.
That article never existed. Move along, now.
Re: This is not the article you are looking for.
We have always been at war with encryption.
More evidence of government and corporate capture of the media
This is yet more evidence of government and corporate capture of the media. Someone, somewhere told them to pull this piece. It had to come from the government.
Re: More evidence of government and corporate capture of the media
You had this right the first time:
Why then this:
Abuse of power by gov’t officials, or deep pocketed advertiser’s nose is out of joint? It could be either. It could even be the editors not wanting to offend one or the other or both.
Well if I was an editor at the Post I suppose I wouldn’t think that highly of Michael “Skeletor” Chertoff and his cronies either. But that’s just missing the point
The dumb bad guys
Not only will the Smart Bad Guys be able to use strong encryption, but they will show the Dumb Bad Guys how to use strong encryption as well.
Only the Good Guys will have weak backdoored cryptography to make the Bad Guys* jobs easier.
* also meaning the government big brother snoops
Minor relevant detail not mentioned in this post
Jeff Bezos now owns Washington Post and has $600M contract with CIA:
http://fair.org/blog/2013/08/06/amazon-wilkileaks-the-washington-post-and-the-cia/
Online Corroborating Evidence
Indirect corroborating evidence online now: Google cache of Omnifeed link to Washington Post article
I’ve copied this just to show what I’m seeing in as of this post. To see for yourself, look in Google’s cache now. Note also that Omnifeed itself has already updated its page to reflect the new Washington Post content.
But this provides some confirmation that the Chertoff/Hayden article was indeed up at the Washington Post site. I myself have no connection with Omnifeed, and in fact had never heard of them or visited their site before today.
Google cache oddities
Anyone understand why Washington Post content is not readily available directly from Google cache?
Re: Google cache oddities
Google doesn’t cache websites that want them to anymore.
Re: Re: Google cache oddities
robots.txt ?
That’s what I’m getting from Internet Archive regarding this Washington Post article.
Re: Re: Google cache oddities
that don’t want them to
Re: Re: Re: Google cache oddities
And s#Chertoff/Hayden#McConnell/Chertoff/Lynn# in my 11:48am post.
Re: Google cache oddities
A paywall, probably.
show the post you have balls america
go make a print out of the original article and glue them to its building, perhaps a few million copies might send them the right message
Bing cache showing inconistent results now
Bing cache is showing inconsistent results for me. I’m getting one view from:
The text in this view appears to corroborate the story—
But when I actually check Bing’s cache, I’m getting the updated contented content as of 7/29/2015. It shows the editor’s note.
Too much javascript on WaPo's site
I had never visited WaPo’s site until they started carrying The Volokh Conspiracy. The first few times I visited my computer went nuts with all the javascript (I have NoScript). And making matters worse: no link to The Volokh Conspiracy on their front page. Even when I figured out the direct link there was so much javascript. Volokh’s old site never had that much.
Maybe it wasn't genuine...
Maybe the article was just fan fiction.
It raises the original crypto wars and the fight over the Clipper Chip, and notes that when that effort failed, “the sky did not fall, and we did not go dark and deaf.”
Talking of the Clipper Chip, I know it was apparently defunct in 1996, but weren’t Nintendo making a big thing about its inclusion in Gamecubes just five years later? 😉
Twitter backtracking
Who is Michael Goldstein? Anyone know him personally?
Re: Twitter backtracking
Gotta be related to Emmanuel Goldstein.
Washington Post
Too bad the Post got rid of its ombudsman; now we’ll probably never get an explaination.
"wasteful idiocy"
One look at history will tell you that wasteful idiocy is probably the thing humanity does best, if only from a lot of repeated practice.
The check to The Chertoff Group from
Google, Apple or Facebook must have bounced.
This certainly shows that there are washington post reporters low on the totem pole that haven’t sold out the public. Seems the higher you go up to the editors the more government collusion and corruption you find. Unsurprising these days.
Yes, the very same Washington Post that has flat out ignored all of the technical expertise on the subject and called for a “golden key” that would let the intelligence community into our communications.
There’s your answer. Does the Washington Post receive any Federal funding, by any chance? Maybe could make a First Amendment case out of this.
Jesus, put your tin foil hats down. The article is back up.
https://www.washingtonpost.com/opinions/the-need-for-ubiquitous-data-encryption/2015/07/28/3d145952-324e-11e5-8353-1215475949f4_story.html
Updated
We’ve added an update now that WaPo has reposted the article:
https://www.washingtonpost.com/opinions/the-need-for-ubiquitous-data-encryption/2015/07/28/3d145952-324e-11e5-8353-1215475949f4_story.html
They claim it was taken down because it was was posted before it had completed the editing process. Anyone able to figure out what edits have been done?
Re: Updated
By eyeball—
• Bio blurbs at top
• Insert “Clinton” in 2nd to last graf
Actually started to use automated tools, but after converting the PDF you provided to text, got stuck on unicode whitespace chars compared to copy of text from Post website.
Probably need to pull out perl to convert—not sure it’s worth it. Anyhow, that’s when I decided eyeball scan would get initial results quicker.
But I’m still not sure of the provenance of your copy. Might have been altered anywhere along the way. Some sort of cache-poisoning attack? Who knows.
Of course they pulled it.
The NSA and FBI both threatened to take the Washington Post off their Christmas card lists.
Update: And… the article has been republished at the Washington Post’s site with a note claiming that it was accidentally published without fully going through its editing process.
“editing”? I think you spelled “vetting” wrong.
Golden key
Why not do a beta test of golden keys with FBI infrastructure only. Then all issues can be verified/hacked….
The internet does not forget.
Re: Re:
So true! Even more, we still practice the old Roman Empire tradition of stirring entrails. You go ahead and un-publish what you mistakenly published. We’ve got our own Wayback Machines containing cached copies of what you no longer want us to see. A few incantations of pdftotext piped through diff, and voila your tap dancing is revealed. Shazam!
There’s a lot of eyeballs out here watching, and apparently you forgot. Mike nailed it before he even showed us what was going on.
You might want to put in a bit more effort next time, and know that you underestimate us at your peril. Have a marvy day!
It is worth noting that this piece is published in today’s printed version of Washington Post (31 July)