{"id":7562,"date":"2014-02-28T07:51:06","date_gmt":"2014-02-28T12:51:06","guid":{"rendered":"http:\/\/www.opensource.im\/?p=7562"},"modified":"2014-02-28T07:51:06","modified_gmt":"2014-02-28T12:51:06","slug":"apple-reveals-algorithm-behind-encrypted-imessages","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/apple-reveals-algorithm-behind-encrypted-imessages.php","title":{"rendered":"Apple reveals algorithm behind &#8216;encrypted&#8217; iMessages"},"content":{"rendered":"<p><p>ANIWashington    Last Updated:February 28, 2014    |17:52 IST            <\/p>\n<p>    Apple has reportedly revealed exactly how secure its iMessage    service is.  <\/p>\n<p>    The iMessage service uses cryptography, which is nothing but a    set of distinct codes assigned as specific keys for each    message sent and received. According to Tech Crunch,    Apple uses public-key cryptography, which is based on a    principle that each message has two keys, one for input and    other for pickup, and unless someone finds a copy of the pickup    key, or find a weakness in the system, there is no way    intercept.  <\/p>\n<p>    When a user first enables iMessage, the device creates two sets    of private and public keys: one set for encrypting data, and    one set for signing data, and if these two keys ever don''t    match up, red flags start going off. The public keys are sent    to Apple's servers, while private keys are stored on the    device.  <\/p>\n<p>    When someone starts an iMessage conversation, they fetch a    user's public key(s) from Apple's servers and before that    message leaves the sender's device, it's encrypted into    something that only the device knows how to decrypt.  <\/p>\n<p>    A user gets one set of keys for each device they add to iCloud,    and each iMessage is encrypted independently for each device    and stored on Apple's servers accordingly.  <\/p>\n<p>    The report said while some data like the timestamp and APN    routing data is not encrypted, all of the independently    encrypted\/non-encrypted data is encrypted as a whole package,    on the trips between a device and Apple's servers.  <\/p>\n<p>    Apple doesn't have any backdoor access to the iMessages sitting    on its servers, tucked into their many-layers-deep encryption.    The company can't read them without a fairly insane amount of    effort.<\/p>\n<p>    For more news from Business Today, follow us on Twitter    @bt_india and on Facebook at facebook.com\/BusinessToday  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Read more:<br \/>\n<a target=\"_blank\" href=\"http:\/\/businesstoday.feedsportal.com\/c\/33681\/f\/593013\/s\/37a39de5\/sc\/4\/l\/0Lbusinesstoday0Bintoday0Bin0Cstory0Capple0Ealgorithm0Eimessages0Eicloud0C10C20A3860A0Bhtml\/story01.htm\/RK=0\/RS=hWNZJjj6tLnon26C6SSExHCQ95o-\" title=\"Apple reveals algorithm behind 'encrypted' iMessages\">Apple reveals algorithm behind 'encrypted' iMessages<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> ANIWashington Last Updated:February 28, 2014 |17:52 IST Apple has reportedly revealed exactly how secure its iMessage service is. The iMessage service uses cryptography, which is nothing but a set of distinct codes assigned as specific keys for each message sent and received<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1600],"tags":[],"class_list":["post-7562","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/7562"}],"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=7562"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/7562\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=7562"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=7562"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=7562"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}