{"id":27663,"date":"2014-11-25T15:41:46","date_gmt":"2014-11-25T20:41:46","guid":{"rendered":"http:\/\/www.opensource.im\/?p=27663"},"modified":"2014-11-25T15:41:46","modified_gmt":"2014-11-25T20:41:46","slug":"hacker-lexicon-what-is-end-to-end-encryption","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/hacker-lexicon-what-is-end-to-end-encryption.php","title":{"rendered":"Hacker Lexicon: What Is End-to-End Encryption?"},"content":{"rendered":"<p><p>    Plenty of companies brag that    their communications app is encrypted. But that marketing claim    demands a followup question: Who has the key? In many cases,    the company itself holds the cryptographic key data that lets    it decrypt your messagesand so, therefore, does any hacker who    compromises the company or government official standing over    its shoulder.  <\/p>\n<p>    But increasingly,    privacy-conscious communications tools are rolling out a    feature known as end-to-end encryption. That end-to-end    promise means that messages are encrypted in a way that allows    only the unique recipient of a message to decrypt it, and not    anyone in between. In other words, only the endpoint computers    hold the cryptographic keys, and the companys server acts as    an illiterate messenger, passing along messages that it cant    itself decipher.  <\/p>\n<p>    That notion of the decryption key    never leaving the users device might seem like a paradox. If    the companys server can never see the key, then how does it    get onto the device when the user installs the app in the first    place?  <\/p>\n<p>    The answer is possible because of    another crypto trick known as public-key encryption. In public    key crypto systems, a program on your computer mathematically    generates a pair of keys. One, called the private key or secret    key, is used for decrypting messages sent to you and never    leaves your device. The other, called the public key, is used    for encrypting messages that are sent to you, and its designed    so that only the corresponding private key can decrypt those    messages. That key can be shared with anyone who wants to    encrypt a message to you. Think of the system like a lockbox on    your doorstep for the UPS delivery man: anyone with your public    key can put something in the box and lock it, but only you have    the private key to unlock it.  <\/p>\n<p>    The first free, widely used    end-to-end encrypted messaging software was PGP, or Pretty Good    Privacy, a program coded by Phil Zimmermann and released in    1991. But its taken decades for that complete encryption    tunnel to reach the masses. Programs like the Off The Record    plugin for Jabber instant-messaging applications and TextSecure    for text messaging have made end-to-end encryption far easier    to use. Apple uses a form of end-to-end encryption in its    iMessage app. (Though some security researchers have pointed to    flaws    in its implementation that might allow its messages to be    decrypted.) Google is experimenting with    an end-to-end encryption email plugin for Chrome. And just    last week smartphone messaging app Whatsapp integrated    TextSecure into its Android software, turning    on end-to-end encryption for hundreds of millions of    users.  <\/p>\n<p>    Even end-to-end encryption isnt    necessarily impervious from snooping. Rather than try to    actually break the encryption, for instance, an eavesdropper    may try to impersonate a message recipient so that messages are    encrypted to their public key instead of the one the sender    intended. After decrypting the message, the snoop can then    encrypt it to the recipients actual public key and send it on    again to avoid detection; this is whats known as a    man-in-the-middle attack. To combat that tactic, some    end-to-end encryption programs generate unique one-time strings    of characters based on the two users public keys. The two    people communicating read out that passphrase to each other    before starting their conversation. If the characters match,    they can be reassured theres no man in the middle.  <\/p>\n<p>    Of course, there are still two    vulnerable points left in even perfect end-to-end encryption    systems: the ends. Each users computer can still be hacked to    steal his or her cryptographic key or simply read the    recipients decrypted messages. Even the most perfectly    encrypted communication pipe is only as secure as the mailbox    on the other end.  <\/p>\n<p>    Hacker Lexicon is WIREDs    explainer series that seeks to de-mystify the jargon of    information security, surveillance and privacy.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>More:<br \/>\n<a target=\"_blank\" href=\"http:\/\/feeds.wired.com\/c\/35185\/f\/661370\/s\/40d2d015\/sc\/4\/l\/0M0Swired0N0C20A140C110Chacker0Elexicon0Eend0Eto0Eend0Eencryption0C\/story01.htm\/RK=0\/RS=za0ik9_douYWSy1zlL9iktUle_k-\" title=\"Hacker Lexicon: What Is End-to-End Encryption?\">Hacker Lexicon: What Is End-to-End Encryption?<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Plenty of companies brag that their communications app is encrypted. But that marketing claim demands a followup question: Who has the key? In many cases, the company itself holds the cryptographic key data that lets it decrypt your messagesand so, therefore, does any hacker who compromises the company or government official standing over its shoulder<\/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-27663","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/27663"}],"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=27663"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/27663\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=27663"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=27663"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=27663"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}