{"id":2723,"date":"2014-02-04T12:52:45","date_gmt":"2014-02-04T17:52:45","guid":{"rendered":"http:\/\/www.opensource.im\/?p=2723"},"modified":"2014-02-04T12:52:45","modified_gmt":"2014-02-04T17:52:45","slug":"cryptography-breakthrough-could-make-software-unhackable","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/cryptography-breakthrough-could-make-software-unhackable.php","title":{"rendered":"Cryptography Breakthrough Could Make Software Unhackable"},"content":{"rendered":"<p><p>    As a graduate student at the Massachusetts Institute of    Technology in 1996, Amit Sahai was fascinated    by the strange notion of a zero-knowledge proof, a type of    mathematical protocol for convincing someone that something is    true without revealing any details of why it is true. As Sahai    mulled over this counterintuitive concept, it led him to    consider an even more daring notion: What if it were possible    to mask the inner workings not just of a proof, but of a    computer program, so that people could use the program without    being able to figure out how it worked?  <\/p>\n<p>    The idea of obfuscating a program had been around for    decades, but no one had ever developed a rigorous mathematical    framework for the concept, let alone created an unassailable    obfuscation scheme. Over the years, commercial software    companies have engineered various techniques for garbling a    computer program so that it will be harder to understand while    still performing the same function. But hackers have defeated    every attempt. At best, these commercial obfuscators offer a    speed bump, said Sahai, now a computer science professor at    the University of California, Los Angeles. An attacker might    need a few days to unlock the secrets hidden in your software,    instead of a few minutes.  <\/p>\n<p>    Secure program obfuscation would be useful for many    applications, such as protecting software patches, obscuring    the workings of the chips that read encrypted DVDs, or    encrypting the software controlling military drones. More    futuristically, it would allow people to create autonomous    virtual agents that they could send out into the computing    cloud to act on their behalf. If, for example, you were    heading to a remote cabin in the woods for a vacation, you    could create and then obfuscate a computer program that would    inform your boss about emails you received from an important    client, or alert your sister if your bank balance dropped too    low. Your passwords and other secrets inside the program would    be safe.  <\/p>\n<p>    You could send that agent into the computing wild, including    onto untrusted computers, Sahai said. It could be captured by    the enemy, interrogated, and disassembled, but it couldnt be    forced to reveal your secrets.  <\/p>\n<p>    As Sahai pondered program obfuscation, however, he and several    colleagues quickly realized that its potential far surpassed    any specific applications. If a program obfuscator could be    created, it could solve many of the problems that have driven    cryptography for the past 40 years  problems about how to    conduct secure interactions with people at, say, the other end    of an Internet connection, whom you may not know or trust.  <\/p>\n<p>    A program obfuscator would be a powerful tool for finding    plausible constructions for just about any cryptographic task    you could conceive of, said Yuval Ishai, of the    Technion in Haifa, Israel.  <\/p>\n<p>    Precisely because of obfuscations power, many computer    scientists, including Sahai and his colleagues, thought it was    impossible. We were convinced it was too powerful to exist,    he said. Their earliest research findings seemed to confirm    this, showing that the most natural form of obfuscation is    indeed impossible to achieve for all programs.  <\/p>\n<p>    Then, on July 20, 2013, Sahai and five co-authors posted a paper on the    Cryptology ePrint Archive demonstrating a candidate protocol    for a kind of obfuscation known as indistinguishability    obfuscation. Two days later, Sahai and one of his co-authors,    Brent Waters,    of the University of Texas, Austin, posted a second paper    that suggested, together with the first paper, that this    somewhat arcane form of obfuscation may possess much of the    power cryptographers have dreamed of.  <\/p>\n<p>    This is the first serious positive result when it comes to    trying to find a universal obfuscator, said Boaz Barak, of Microsoft    Research in Cambridge, Mass. The cryptography community is    very excited. In the six months since the original paper was    posted, more papers have appeared on the ePrint archive with    obfuscation in the title than in the previous 17 years.  <\/p>\n<p>    However, the new obfuscation scheme is far from ready for    commercial applications. The technique turns short, simple    programs into giant, unwieldy albatrosses. And the schemes    security rests on a new mathematical approach that has not yet    been thoroughly vetted by the cryptography community. It has,    however, already withstood the first attempts to break it.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Excerpt from:<br \/>\n<a target=\"_blank\" href=\"http:\/\/feeds.wired.com\/c\/35185\/f\/661370\/s\/36ab1dd5\/sc\/32\/l\/0L0Swired0N0Cwiredscience0C20A140C0A20Ccryptography0Ebreakthrough0C\/story01.htm\" title=\"Cryptography Breakthrough Could Make Software Unhackable\">Cryptography Breakthrough Could Make Software Unhackable<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> As a graduate student at the Massachusetts Institute of Technology in 1996, Amit Sahai was fascinated by the strange notion of a zero-knowledge proof, a type of mathematical protocol for convincing someone that something is true without revealing any details of why it is true. <\/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-2723","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/2723"}],"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=2723"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/2723\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=2723"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=2723"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=2723"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}