{"id":31531,"date":"2017-03-01T17:41:18","date_gmt":"2017-03-01T22:41:18","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/after-3-years-why-gmails-end-to-end-encryption-is-still-vapor-wired.php"},"modified":"2017-03-01T17:41:18","modified_gmt":"2017-03-01T22:41:18","slug":"after-3-years-why-gmails-end-to-end-encryption-is-still-vapor-wired","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/after-3-years-why-gmails-end-to-end-encryption-is-still-vapor-wired.php","title":{"rendered":"After 3 Years, Why Gmail&#8217;s End-to-End Encryption Is Still Vapor &#8211; WIRED"},"content":{"rendered":"<p><p>          Slide:          1 \/          of 1. Caption: Caption: reuseok encrypt          security abstract color code privacy fence google          Katherine          Lubar\/Getty Images        <\/p>\n<p>    Nearly three years have passed since Google announced it would    offer an end-to-end encryption add-on for Gmail, a potentially    massive shift in the privacy options of a piece of software    used by more than a billion people. It still hasnt    materialized. And while Google insists its    encryptionplugin isnt vaporware, the companys latest    move has left critics with the distinct impression that Gmails    end-to-end encrypted future looks cloudy at bestif not    altogether evaporated.  <\/p>\n<p>    LastFriday, Google quietly announced that E2EMail, an    extension for Chrome that would seamlessly encrypt and decrypt    Gmail messages, was no longer a Google effort. Instead, the    company has invited the outside developer community to adopt    the projects open-source code. Google was careful to    emphasize in a blog post describing the change that it    hasnt given up work on its email encryption tool. But    cryptographers and members of the privacy community see the    move as confirmation that Google has officially backburnered a    critical privacy and security initiative.  <\/p>\n<p>    The real message is that theyre not actively developing this    as a Google project anymore, says Matthew Green, a    cryptographer and computer scientist at Johns Hopkin University    who has closely studied tech firms messaging encryption    products. Green notes that after close to three years, hes    happy to see any code come out of Googles Gmail encryption    work. But its hardly the finishedemail-encrypting plugin    that Google had promised. Its definitely a bit of a    disappointment, given how much hype Google generated around    this project at one point, to see that theyre not pursuing    this as a core feature of Gmail, Green says.  <\/p>\n<p>    When Google first announced in June of 2014 that it    would build an encryption tool for Gmailthen known as    End-to-Endthe move was seen as part of Googles    dramaticresponse to the NSA surveillance revealed by    leaker Edward Snowden. But the projects failure    to emerge from a research phaseeven as communications like    Apples iMessage, Facebook Messenger, Facebook-owned WhatsApp, and even Viber offer     end-to-end encryption to their hundreds of millions or    billions of usershas disillusioned the privacy community.    Commenters on the projects Github page have asked for more than a year if Google has    abandoned the encryption extension.  <\/p>\n<p>    Googles decision to hand E2Email over to open-source    developers only cements that perception. If I had to place a    bet, Id say its a telltale sign the project isnt going    anywhere, says web security researcher Jeremiah Grossman,    chief of security strategy at security firm Sentinel One. This    is a way for them to get their work out there but to absolve    themselves of future obligations.  <\/p>\n<p>    Green, who has spoken to Google engineers about the project,    says the End-to-End initiative never received the staffing    necessary to push it forward. Today, he says, the total    attention Google devotes to the project equates to a fraction    of a single full-time staffer. The upshot is that Google wont    be doing much more on end-to-end encryption, Green says.  <\/p>\n<p>    Googles own security engineers, meanwhile, say that theyve    hardly abandoned their encryption push. But making email    encryption easy, argues Google privacy and security product    manager Stephan Somogyi, isfar harder than it might seem    to the public. Unlike WhatsApp or Facebook Messenger,    GmailsEnd-to-Endproject sought to bolt encryption    onto email, an old protocol that still has to interoperate with    billions of clients outside of Googles control. And    Somogyipoints out that his engineers have also had to    build and refine an entirely new library of crypto code in    javascript, a necessary stepping stone for secure web-based    encryption tools, and one widely believed to be unworkable a few years ago.  <\/p>\n<p>    More recently, he says, the team has focused on the larger    problem of key managementthe tricky task of securely    distributing, tracking, and looking up the unique encryption    keys that allow users to decrypt encrypted messages and prove    their identities. That problem has for decades dogged PGP, the    encryption scheme Google bases its Gmail encryption project on.    Googles engineers are now working to solve it with a project    called Key Transparency, along with researchers at    Princeton, Yahoo, and Open Whisper Systems.  <\/p>\n<p>    The magic needs to happen in key distribution and key    discovery, and weve been quiet for so long because weve been    working on that hard stuff, says Somogyi. But hemakes no    promises that more rigorous approach will produce actual,    working encryption tools for Gmail any time soon. Even once    Key Transparency is out the door, theres other hard stuff to    work on.  <\/p>\n<p>    The decision to open-source the Gmail encryption plug-in    project, Somogyi says, was a recognition that outside    developers might want to put out a quicker fix rather than    solve the underlying problems his engineers have focused on.    Were very much playing the long game, Somogyi says. The    reason we want to put this into the open source community is    precisely because everyone cares about this so much. We dont    want everyone waiting for Google to get something done.  <\/p>\n<p>    Despite those efforts, however, Google hasnt kept up with its    competitors onend-to-end encrypted messaging. Its only    serious effort in the last year was to offer     opt-in end-to-end encryption in its Allo messenger, a new    service with an infinitesimal fraction of the user base of    existing chat platforms like Google Hangouts and Gchat.  <\/p>\n<p>    As Gmails long-awaited end-to-end encryption features have    failed to appear, critics have speculated about Googles    motives. Does it want to avoid the clashes with the US    government that WhatsApp and Apple faced down when their    encryption has stymied law enforcement? Or does a company so    focused on big data analysis not want to relinquish its ability    to mine emails in the service of highly targeted ads and    services? The Allo voice assistant, for instance, doesnt    function when users haveencryption enabled. The entire    notion of end-to-end encryption, after all, is that no one but    the people communicating can decrypt messages,    noteventhe service hosting those communications.  <\/p>\n<p>    Googles Somogyi argues that advertising doesnt figure into    his teams encryption decisions. But he concedes that for    services like Gmails spam and malware filtering, end-to-end    encryption makes data mining far more difficult. He describes    the balance Google seeks diplomatically: Where we can provide    added value to the user by having machine-based systems look at    the data, were absolutely going to do that, Somogyi said. At    every opportunity that we have to protect users data from    unauthorized access we absolutely, vigorously pursue that.  <\/p>\n<p>    Ideally, the tradeoffs between services that mine someones    communications and their privacy should be left to the users    themselves, says Somogyi. Whats important ultimately is that    the user has a choice, he says.  <\/p>\n<p>    That choice, for Gmail users, has been a long time coming.    Until the E2Email project comes to fruitionif it ever doesthe    existing decision for users is starker: Share your secrets over    Gmail, or send them over one of the many end-to-end encrypted    messaging services thats far better engineeredto protect    them.  <\/p>\n<p>    Updated 2\/28\/2017 1:10pm EST to clarify that while Gmail    does use some forms of encryption, it doesnt offer end-to-end    encryption that ensures only the people communicating can    decrypt messages.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Read the original here:<br \/>\n<a target=\"_blank\" href=\"https:\/\/www.wired.com\/2017\/02\/3-years-gmails-end-end-encryption-still-vapor\/\" title=\"After 3 Years, Why Gmail's End-to-End Encryption Is Still Vapor - WIRED\">After 3 Years, Why Gmail's End-to-End Encryption Is Still Vapor - WIRED<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Slide: 1 \/ of 1. Caption: Caption: reuseok encrypt security abstract color code privacy fence google Katherine Lubar\/Getty Images Nearly three years have passed since Google announced it would offer an end-to-end encryption add-on for Gmail, a potentially massive shift in the privacy options of a piece of software used by more than a billion people. <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[45],"tags":[],"class_list":["post-31531","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31531"}],"collection":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/comments?post=31531"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31531\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=31531"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=31531"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=31531"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}