{"id":28009,"date":"2014-12-12T20:41:01","date_gmt":"2014-12-13T01:41:01","guid":{"rendered":"http:\/\/www.opensource.im\/?p=28009"},"modified":"2014-12-12T20:41:01","modified_gmt":"2014-12-13T01:41:01","slug":"people-want-safe-communications-not-usable-cryptography","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/people-want-safe-communications-not-usable-cryptography.php","title":{"rendered":"People Want Safe Communications, Not Usable Cryptography"},"content":{"rendered":"<p><p>    For encryption to be widely used, it must be built into    attractive, easy-to-use apps like those people already rely on.  <\/p>\n<p>    Security and privacy expert Micah Lee recently described how he    helped set up cryptographically protected communications    between whistleblower Edward Snowden and the journalists Glenn    Greenwald and Laura Poitras, who would share what he had    learned about the NSAs surveillance programs with the world.    Lees tale of how the three struggled to master the technology    was an urgent reminder of a problem that has bugged me for a    while and has implications for anyone who wants to ensure the    privacy of personal or professional matters.  <\/p>\n<p>    The cryptographic software we have today hobbles those who try    to use it with Rube Goldberg-machine complexity and academic    language as dated as a pair of Jordache jeans. Snowden,    Poitras, and Greenwalds tussles with that problem could    conceivably have foiled Snowdens attempts to communicate    safely, leaving the world in the dark about U.S. surveillance    practices and their effects on our security and privacy.  <\/p>\n<p>    Why is encryption software so horrid to use? Because theres no    such thing as usable cryptography, despite growth in popularity    of the buzzword usable crypto among experts in recent years.    Usability and crypto are in fact two separate disciplines. One    is about crafting things that people interact with; the other    is concerned with technical plumbing that, although crucial,    should not be visible to the end user. Unless we find the right    balance, consumers will never benefit from crypto.  <\/p>\n<p>    The cypherpunk dreamwhere crypto is ubiquitous and    everyone speaks code as a second languagenever reached    fruition because we cryptographers mistook our goal for our    consumers goal. Johnny cant encrypt because Johnny never    wanted to encrypt. Nobody really wants cryptography in and of    itself. What they want is to communicate how, and with whom,    they please, but safely.  <\/p>\n<p>    Cryptographers and the security and privacy community cant fix    this problem by ourselves. Real-world cryptography isnt only    about cryptography. Its just as much about product design, and    building experiences that work for the usernot    requiring work from the user. Its a cross-discipline    problem that requires not only cryptographers but    user-experience designers and developers, too.  <\/p>\n<p>    Equivalent problems have been more or less solved in other    areas of computing. The e-mail encryption system PGP debuted in    1991, the same year as Linux and the World Wide Web. The last    two have evolved to become central to many services and    products with hundreds of millions of nonexpert users. But when    you try to use PGP or its open-source cousin, GPG, you will    find yourself in many ways stuck in 1991as Snowden and his    contacts discovered.  <\/p>\n<p>    One way we can start to solve this problem is by adapting a    common tool in security circles, the security audit, where an    applications vulnerability to attacks is investigated through    a variety of technical processes. Recently, campaigners have    raised money to fund security audits of critical tools such as    the hard-drive encryption software TrueCrypt. I suggest we    use the same model to fund user-experience audits of secure    communication software, and subject our tools to the kind of    user testing that hones the blockbuster apps of leading    consumer companies.  <\/p>\n<p>    We also need to change how we talk to users about cryptographic    concepts and security, and to set up places for    cross-discipline research into how to craft friendly user    experiences underpinned by security and privacy technologies.  <\/p>\n<p>    Right now, things are bad, but inconsistently promising. The    Open    WhisperSystems project has made mobile apps for encrypted    messaging and calls that appear much like normal apps for    voice and text, and recently it announced it is helping    WhatsApp encrypt its users messages. We have new    organizations like Simply Secure, which aims to foster the development of    usable security and privacy software (and is led by a product    designer, not a cryptographer).  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Read this article:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.technologyreview.com\/view\/533456\/people-want-safe-communications-not-usable-cryptography\" title=\"People Want Safe Communications, Not Usable Cryptography\">People Want Safe Communications, Not Usable Cryptography<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> For encryption to be widely used, it must be built into attractive, easy-to-use apps like those people already rely on. Security and privacy expert Micah Lee recently described how he helped set up cryptographically protected communications between whistleblower Edward Snowden and the journalists Glenn Greenwald and Laura Poitras, who would share what he had learned about the NSAs surveillance programs with the world. <\/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-28009","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/28009"}],"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=28009"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/28009\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=28009"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=28009"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=28009"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}