{"id":29782,"date":"2015-03-16T08:41:09","date_gmt":"2015-03-16T12:41:09","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/yahoo-puts-email-encryption-plugin-source-code-up-for-review.php"},"modified":"2015-03-16T08:41:09","modified_gmt":"2015-03-16T12:41:09","slug":"yahoo-puts-email-encryption-plugin-source-code-up-for-review","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/yahoo-puts-email-encryption-plugin-source-code-up-for-review.php","title":{"rendered":"Yahoo puts email encryption plugin source code up for review"},"content":{"rendered":"<p><p>    Yahoo released the source    code for a plugin that will enable end-to-end encryption of    email messages, a planned data-security improvement prompted by    disclosures of U.S. National Security Agency snooping.  <\/p>\n<p>    The company is asking    security experts to look at its code, published on GitHub,    and report vulnerabilities, wrote Alex Stamos, Yahoos chief    information security officer, in a     blog post.  <\/p>\n<p>    The plugin should be ready by    year end, wrote Stamos, who gave a presentation on Sunday at    the South by Southwest conference in Austin, Texas.  <\/p>\n<p>    Yahoo and Google have been    collaborating to make their email systems compatible with    end-to-end encryption, a technology based on the public-key    cryptography standard OpenPGP. End-to-end encryption is not    widely used, as it can be difficult for non-technical users to    set up.  <\/p>\n<p>    The technology encrypts a    messages contents so only the sender and recipient can read    it. A messages subject line is not encrypted, however, and    neither is the routing metadata, which cant be scrambled since    it is needed in order to send a message.  <\/p>\n<p>    A video included in the post    by Stamos showed how someone could set up an encrypted message    much faster using the companys plugin versus using GPG Suite, a software package for    sending encrypted email on Apples OS X.  <\/p>\n<p>    Yahoo vowed to improve its    data security after documents leaked by former NSA contractor    Edward Snowden showed the spy agency had penetrated the    companys networks as well as those of many others, including    Google.  <\/p>\n<p>    Email encryption is one of a    number of security improvements Yahoo and Google have    undertaken.  <\/p>\n<p>    In March 2014, Yahoo began    encrypting traffic flowing between its data centers after    information from Snowden indicated the     NSA had access to those connections.  <\/p>\n<p>    Google also encrypts    connections between its data centers. Like Yahoo, the company    has published its Chrome extension for    end-to-end encryption on GitHub as well.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>See the article here:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.pcworld.com\/article\/2897132\/yahoo-puts-email-encryption-plugin-source-code-up-for-review.html\/RK=0\/RS=BS8msmz1b2O8ARxfo.0bg_GEJLM-\" title=\"Yahoo puts email encryption plugin source code up for review\">Yahoo puts email encryption plugin source code up for review<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Yahoo released the source code for a plugin that will enable end-to-end encryption of email messages, a planned data-security improvement prompted by disclosures of U.S. National Security Agency snooping. The company is asking security experts to look at its code, published on GitHub, and report vulnerabilities, wrote Alex Stamos, Yahoos chief information security officer, in a blog post<\/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-29782","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29782"}],"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=29782"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29782\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=29782"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=29782"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=29782"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}