{"id":31488,"date":"2017-02-24T19:49:29","date_gmt":"2017-02-25T00:49:29","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/googles-collision-shakes-up-computer-cryptography-pc-magazine.php"},"modified":"2017-02-24T19:49:29","modified_gmt":"2017-02-25T00:49:29","slug":"googles-collision-shakes-up-computer-cryptography-pc-magazine","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/googles-collision-shakes-up-computer-cryptography-pc-magazine.php","title":{"rendered":"Google&#8217;s Collision Shakes Up Computer Cryptography &#8211; PC Magazine"},"content":{"rendered":"<p><p>    A cryptographic hash collision suggests the SHA-1 standardused    to authenticate documentscan be hacked.  <\/p>\n<p>    Google researchers have engineered an extremely rare and    invisible collision, but they didn't need the     Large Hadron Collider to do it.  <\/p>\n<p>    That's because their collision isn't atomic, it's    cryptographic: after years of trying, Google found a way to    crack the SHA-1 cryptographic hash function, a security    building block that enables digital signatures and HTTPS    encryption.  <\/p>\n<p>    Cracking SHA-1 requires creating a cryptographic hash    collision, which is essentially when a single hash, or \"digest\"    applies to two different files.  <\/p>\n<p>    \"A collision occurs when two distinct pieces of dataa    document, a binary, or a website's certificatehash to the same    digest,\" Google explained in a blog post. \"In practice, collisions should    never occur for secure hash functions. However if the hash    algorithm has some flaws, as SHA-1 does, a well-funded attacker    can craft a collision.\"  <\/p>\n<p>    The danger of a collision is much the same as weak encryption:    hackers could exploit it. In this case, they could use a    collision to trick a system into accepting a malicious document    or other file using the hash of a benign one.  <\/p>\n<p>    Google's collision comes more than 20 years after SHA-1 was    first introduced, and suggests that the standard isn't secure    enough to handle sensitive information. To prove their    collision, Google's researchers provided two PDFs that have    identical SHA-1 hashes but different content.  <\/p>\n<p>    \"We hope that our practical attack against SHA-1 will finally    convince the industry that it is urgent to move to safer    alternatives such as SHA-256,\" Google wrote.  <\/p>\n<p>    Other security experts agree: in light of Google's findings,    password management company LastPass said it would be accelerating its    retirement of SHA-1. LastPass, the Google Chrome browser, and    much of the rest of the Internet is gradually moving to the    SHA-256 encryption standard.  <\/p>\n<p>      Tom is PCMag's San Francisco-based news reporter. He got his      start in technology journalism by reviewing the latest hard      drives, keyboards, and much more for PCMag's sister site,      Computer Shopper. As a freelancer, he's written on topics as      diverse as Borneo's rain forests, Middle Eastern airlines,      and big data's role in presidential elections. A graduate of      Middlebury College, Tom also has a master's journalism degree      from New York University. Follow him on Twitter @branttom.      More    <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Original post:<br \/>\n<a target=\"_blank\" href=\"http:\/\/www.pcmag.com\/news\/351978\/googles-collision-shakes-up-computer-cryptography\" title=\"Google's Collision Shakes Up Computer Cryptography - PC Magazine\">Google's Collision Shakes Up Computer Cryptography - PC Magazine<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> A cryptographic hash collision suggests the SHA-1 standardused to authenticate documentscan be hacked. Google researchers have engineered an extremely rare and invisible collision, but they didn't need the Large Hadron Collider to do it<\/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-31488","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31488"}],"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=31488"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31488\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=31488"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=31488"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=31488"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}