{"id":29409,"date":"2015-02-27T12:40:56","date_gmt":"2015-02-27T17:40:56","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/how-to-sabotage-encryption-software-and-not-get-caught.php"},"modified":"2015-02-27T12:40:56","modified_gmt":"2015-02-27T17:40:56","slug":"how-to-sabotage-encryption-software-and-not-get-caught","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/how-to-sabotage-encryption-software-and-not-get-caught.php","title":{"rendered":"How To Sabotage Encryption Software (And Not Get Caught)"},"content":{"rendered":"<p><p>    In the field of cryptography, a    secretly planted backdoor that allows eavesdropping on    communications is usually a subject of paranoia and dread. But    that doesnt mean cryptographers dont appreciate the art of    skilled cyphersabotage. Now one group of crypto experts has    published an appraisal of different methods of weakening crypto    systems, and the lesson is that some backdoors are clearly    better than othersin stealth, deniability, and even in    protecting the victims privacy from spies other than    thebackdoors creator.  <\/p>\n<p>    In a paper titled Surreptitiously    Weakening Cryptographic Systems, well-known cryptographer and    author Bruce Schneier and researchers from the Universities of    Wisconsin and Washington take the spys view to the problem of    crypto design: What kind of built-in backdoor surveillance    works best?  <\/p>\n<p>    Their paper analyzes and rates    examples of both intentional and seemingly unintentional flaws    built into crypto systems over the last two decades. Their    results seem to imply, however grudgingly, that the NSAs most    recent known method of sabotaging encryption may be the best    option, both in effective, stealthy surveillance and in    preventing collateral damage to the Internets security.  <\/p>\n<p>    This is a guide to creating    better backdoors. But the reason you go through that exercise    is so that you can create better backdoor protections, says    Schneier, the author of the recent book Data and    Goliath, on corporate and government surveillance. This    is the paper the NSA wrote two decades ago, and the Chinese and    the Russians and everyone else. Were just trying to catch up    and understand these priorities.  <\/p>\n<p>    The researchers looked at a    variety of methods of designing and implementing crypto systems    so that they can be exploited by eavesdroppers. The methods    ranged from flawed random number generation to leaked secret    keys to codebreaking techniques. Then the researchers rated    them on variables like undetectability, lack of conspiracy (how    much secret dealing it takes to put the backdoor in place),    deniability, ease of use, scale, precision and control.  <\/p>\n<p>    Heres the full chart of those    weaknesses and their potential benefits to spies. (The    ratingsL, M, and H stand for Low, Medium and    High.)  <\/p>\n<\/p>\n<p>    A bad random number generator, for    instance, would be easy to place in softwarewithout many    individuals involvement, and if it were discovered, could be    played off as a genuinecoding error rather than a    purposeful backdoor. As an example of this, the researchers    point to an implementation of Debian    SSL in 2006 in which two lines of code were commented out,    removing a large source of the entropy needed to create    sufficiently random numbers for the systems encryption. The    researchers acknowledge that crypto sabotagewas almost    certainly unintentional, the result of a programmer trying to    avoid a warning message from a security tool. But the flaw    nonetheless required the involvement of only one coder, went    undiscovered for two years, and allowed a full break of    Debians SSL encryption for anyone aware of the bug.  <\/p>\n<p>    Another, even subtler method of    subverting crypto systemsthat the researchers suggest is    what they call implementation fragility, which amounts to    designing systemsso complex and difficult that coders    inevitably leave exploitable bugs in the software that uses    them. Many important standards such as IPsec, TLS and others    are lamented as being bloated, overly complex, and poorly    designedwith responsibility often laid at the public    committee-oriented design approach, the researchers write.    Complexity may simply be a fundamental outcome of    design-by-committee, but a saboteur might also attempt to steer    the public process towards a fragile design. Thatkind of    sabotage, if it were found, would be easily disguisedas    the foibles of a bureaucratic process.  <\/p>\n<p>    But when it comes to a rating for    controlthe ability to distinguish who will be able to    exploit the security weakness youve insertedthe researchers    label implementation fragility and bad number generation as    low.Use a bad random number generator or fragile crypto    implementation, and any sufficiently skilled cryptanalysts who    spot the flaw will be able to spy on your target. Its clear    that some of these thingsare disastrous in terms of    collateraldamage, says paper co-author University of    Wisconsin computer scientist Thomas Ristenpart. If you have a    saboteur leaving vulnerabilities in criticalsystem that    can be exploited by anyone, then this is just disastrous for    the security of consumers.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>More here:<br \/>\n<a target=\"_blank\" href=\"http:\/\/feeds.wired.com\/c\/35185\/f\/661467\/s\/43ddb089\/sc\/4\/l\/0L0Swired0N0C20A150C0A20Csabotage0Eencryption0Esoftware0Eget0Ecaught0C\/story01.htm\/RK=0\/RS=nI49je4NGoufz4KYU2vmxDfsUUA-\" title=\"How To Sabotage Encryption Software (And Not Get Caught)\">How To Sabotage Encryption Software (And Not Get Caught)<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> In the field of cryptography, a secretly planted backdoor that allows eavesdropping on communications is usually a subject of paranoia and dread. But that doesnt mean cryptographers dont appreciate the art of skilled cyphersabotage. <\/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-29409","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29409"}],"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=29409"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/29409\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=29409"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=29409"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=29409"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}