{"id":33039,"date":"2017-08-18T11:44:09","date_gmt":"2017-08-18T15:44:09","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/encryption-key-for-iphone-5s-touch-id-exposed-opens-door-to-appleinsider-press-release-blog.php"},"modified":"2017-08-18T11:44:09","modified_gmt":"2017-08-18T15:44:09","slug":"encryption-key-for-iphone-5s-touch-id-exposed-opens-door-to-appleinsider-press-release-blog","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/encryption-key-for-iphone-5s-touch-id-exposed-opens-door-to-appleinsider-press-release-blog.php","title":{"rendered":"Encryption key for iPhone 5s Touch ID exposed, opens door to &#8230; &#8211; AppleInsider (press release) (blog)"},"content":{"rendered":"<p><p>    By Mike    Wuerthele    Thursday, August 17, 2017, 11:14 am PT    (02:14 pm ET)  <\/p>\n<p>    First spotted by Redmond Pie     on Wednesday, Twitter user \"xerub\" posted the information,    and an extraction tool for the Secure Enclave firmware, in    advance of the Singapore Hack in the Box conference.  <\/p>\n<p>    The tool and hack is not for the inexperienced. The outputs of    the tool are binaries of the kernel and related software    regulating the communications between the Touch ID sensor and    Secure Enclave but not any information transmitted presently    or in the past between the Touch ID sensor and the Secure    Enclave.  <\/p>\n<p>    The exposure of how to extract the encryption key from an    iPhone 5s does not mean that the device is no longer secure.    However, it does mean that people angling to make exploits for    the device are able to examine the Secure Enclave firmware on    the device in more detail than previously possible.  <\/p>\n<p>    At present, there is no known exploit utilizing the tool, or    the gleaned data, and it is not clear how one would even be    produced or installed on a target device. Any exploit developed    with the tool would be specific to the iPhone 5s, and require    physical access to the device to load custom firmware as well.  <\/p>\n<p>    Apple's Secure Enclave is in Apple's A7 processor and later and    provides all cryptographic operations for data protection in    iOS devices. The Secure Enclave utilizes its own secure boot    and can be updated using a personalized software update process    that is separate from the application processor which is how    any exploit would have to be installed, one device at a time.  <\/p>\n<p>    The Secure Enclave is responsible for processing fingerprint    data from the Touch ID sensor, determining if there is a match    against registered fingerprints, and then enabling access. Each    pairing of the Touch ID uses the shared encryption key, and a    random number to generate that session's full encryption key.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Read the original:<br \/>\n<a target=\"_blank\" href=\"http:\/\/appleinsider.com\/articles\/17\/08\/17\/encryption-key-for-iphone-5s-touch-id-exposed-opens-door-to-further-research\" title=\"Encryption key for iPhone 5s Touch ID exposed, opens door to ... - AppleInsider (press release) (blog)\">Encryption key for iPhone 5s Touch ID exposed, opens door to ... - AppleInsider (press release) (blog)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> By Mike Wuerthele Thursday, August 17, 2017, 11:14 am PT (02:14 pm ET) First spotted by Redmond Pie on Wednesday, Twitter user \"xerub\" posted the information, and an extraction tool for the Secure Enclave firmware, in advance of the Singapore Hack in the Box conference. The tool and hack is not for the inexperienced. The outputs of the tool are binaries of the kernel and related software regulating the communications between the Touch ID sensor and Secure Enclave but not any information transmitted presently or in the past between the Touch ID sensor and the Secure Enclave. <\/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-33039","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/33039"}],"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=33039"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/33039\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=33039"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=33039"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=33039"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}