{"id":31330,"date":"2017-02-13T18:54:28","date_gmt":"2017-02-13T23:54:28","guid":{"rendered":"http:\/\/www.opensource.im\/uncategorized\/four-questions-for-jean-philippe-aumasson-webworkerdaily.php"},"modified":"2017-02-13T18:54:28","modified_gmt":"2017-02-13T23:54:28","slug":"four-questions-for-jean-philippe-aumasson-webworkerdaily","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/cryptography\/four-questions-for-jean-philippe-aumasson-webworkerdaily.php","title":{"rendered":"Four Questions For: Jean-Philippe Aumasson &#8211; WebWorkerDaily"},"content":{"rendered":"<p><p>    Long term, who wins: the cryptographers or the code    breakers?  <\/p>\n<p>    Nobody breaks codes anymore, strictly speaking. When you hear    about broken crypto, its most of the time about bugs in the    implementation or about the use of insecure algorithms. For    example, the DROWN attack that just won the Pwnie Award of the    Best Cryptographic Attack at Black Hat USA exploits weaknesses    in: 1) a protocol already known to be shaky, and 2) an    algorithm already known to be insecure. So weve got    unbreakable crypto, we just need to learn how to use it.  <\/p>\n<p>    What innovations in cybersecurity should companies    implement today?  <\/p>\n<p>    The hot topic in my field is end-to-end encryption, or    encryption all the way from the senders device to the    recipients device. This is therefore the strongest form of    encryption. WhatsApp and Facebook recently integrated    end-to-end encryption in their messaging platforms for the    benefit of their users privacy. Enterprise encryption software    lags behind, however, with encryption solutions that often    expose the unencrypted data to an intermediate server. Thats    acceptable, for example, for compliance or controllability    reasons, but otherwise you should make sure that you use    end-to-end encryption to protect sensitive information, such as    VoIP phone calls (telecommunication standards, including the    latest LTE, are not end-to-end encrypted).  <\/p>\n<p>    What are the implications of mobile technology and    wearables in personal security?  <\/p>\n<p>    Companies creating those products often neglect security and    privacy concerns to save cost (or through ignorance) while    security experts tend to exaggerate these concerns. Well have    to find a middle ground between the needs and expectations of    users and regulations. Meanwhile, the lack of security in IoT    systems creates great opportunities for conference talks and    marketing FUD.  <\/p>\n<p>    In the Internet of things, is everything hackable, and    if so, will someone hack all the pacemakers some day and turn    them off?  <\/p>\n<p>    The everything is hackable mantra is actually less scary than    it sounds. Literally everything is hackable: from your    refrigerators micro controller to your mobile phone, as long    as you put enough effort in it. One shouldnt think in terms of    mere possibility but instead in terms of risk and economic    interests: if I spend X days and Y dollars to hack a pacemaker,    will my profit be worth the X-day and $Y investment? A secure    pacemaker is obviously better than an insecure one, but the    scenario you describe is unlikely to happen; it would just make    a great movie plot.  <\/p>\n<p>    Jean-Philippe (JP) Aumasson is Principal Cryptographer at    Kudelski Security, and holds a PhD in applied cryptography from    EPFL. Switzerland. He has talked at top-tier information    security conferences such as Black Hat, DEFCON, and RSA about    applications of cryptography and quantum technologies. He    designed the popular cryptographic algorithms BLAKE2 and    SipHash, and organized the Password Hashing Competition    project. He wrote the 2015 book The Hash Function BLAKE, and    is currently writing a book on modern cryptography for a    general audience. JP tweets as @veorq.  <\/p>\n<p>    Tags    cryptography Cybersecurity Encryption    end-to-end encryption enterprise encryption Hackers    jean-philippe aumasson  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>See more here:<br \/>\n<a target=\"_blank\" href=\"https:\/\/gigaom.com\/2017\/02\/13\/four-questions-for-jean-philippe-aumasson\/\" title=\"Four Questions For: Jean-Philippe Aumasson - WebWorkerDaily\">Four Questions For: Jean-Philippe Aumasson - WebWorkerDaily<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Long term, who wins: the cryptographers or the code breakers? Nobody breaks codes anymore, strictly speaking. When you hear about broken crypto, its most of the time about bugs in the implementation or about the use of insecure algorithms<\/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-31330","post","type-post","status-publish","format-standard","hentry","category-cryptography"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31330"}],"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=31330"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/31330\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=31330"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=31330"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=31330"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}