{"id":31471,"date":"2017-02-24T01:49:41","date_gmt":"2017-02-24T06:49:41","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/sha-1-crypto-algorithm-is-dead-by-collision-attack-cyberscoop.php"},"modified":"2017-02-24T01:49:41","modified_gmt":"2017-02-24T06:49:41","slug":"sha-1-crypto-algorithm-is-dead-by-collision-attack-cyberscoop","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/sha-1-crypto-algorithm-is-dead-by-collision-attack-cyberscoop.php","title":{"rendered":"SHA-1 crypto algorithm is dead by collision attack &#8211; CyberScoop"},"content":{"rendered":"<p><p>    TheSHA-1    cryptographic hash functionis dead.  <\/p>\n<p>    A24-year-old security mechanism still in wide use around    the internet today, the NSA-developed cryptographic algorithm    was finally proven to be broken this week by a team of Dutch    cryptographers and Google researchers who published their work    atshattered.io. The    researchers showed how to collide two different files but    come out with the same digital signature, showing once and for    all that the SHA-1 algorithm suffers from fatal weaknesses and    can no longer effectively be trusted as a cryptographic    signature guaranteeing the veracity of files.  <\/p>\n<p>    You can read the full    research paper here. The attack, which took the equivalent    of 110 years of single-GPU computations and 6,500 years of    single-CPU computations, has never been spotted in the wild.  <\/p>\n<p>    Although SHA-1 was officially     deprecated by NIST in 2011, its still used widely in    digital certificates, software management and encryption    programs. Cryptographic algorithms are used as crucial bulwarks    of security. When the MD5 algorithm was     broken in 2010, nation-state attackers forged Microsofts    signature and could then hijack Windows update impacting    millions of users, making the infiltration of targeted networks    a far more obtainable task.  <\/p>\n<p>    In 2012, when the death of SHA-1 was still just a hypothetical,    researchers warned of the consequences.  <\/p>\n<p>    When it does happen, its going to be a disaster, because SHA1    is everywhere, Matthew Green, a cryptography professor at    Johns Hopkins University,     toldArs Technica. You could be Microsoft, you could    be Google, if you were able to get an attack on SHA-1.  <\/p>\n<p>    The cryptographer Bruce Schenier     recommendedthat same year to begin migration away    from SHA-1 as quickly as possible.  <\/p>\n<p>    As of Friday, both Chrome and Firefox will     automatically protectusers from insecure TLS\/SSL    certificates. Files sent in Gmail and Google Drive are already    subject to testing against the attack.  <\/p>\n<p>    The researchers point to safer alternatives, such as SHA-256 or    SHA-3. Other experts suggest looking at speedier functions like    Blake2. Whatever the choice,    the lesson is clear: Change or be a soft target.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>See the rest here:<br \/>\n<a target=\"_blank\" href=\"https:\/\/www.cyberscoop.com\/sha-1-crypto-algorithm-is-dead-by-collision-attack\/\" title=\"SHA-1 crypto algorithm is dead by collision attack - CyberScoop\">SHA-1 crypto algorithm is dead by collision attack - CyberScoop<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> TheSHA-1 cryptographic hash functionis dead. A24-year-old security mechanism still in wide use around the internet today, the NSA-developed cryptographic algorithm was finally proven to be broken this week by a team of Dutch cryptographers and Google researchers who published their work atshattered.io. <\/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-31471","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31471"}],"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=31471"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31471\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=31471"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=31471"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=31471"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}