{"id":26816,"date":"2014-10-17T16:40:45","date_gmt":"2014-10-17T20:40:45","guid":{"rendered":"http:\/\/www.opensource.im\/?p=26816"},"modified":"2014-10-17T16:40:45","modified_gmt":"2014-10-17T20:40:45","slug":"us-government-fines-intels-wind-river-over-crypto-exports","status":"publish","type":"post","link":"https:\/\/euvolution.com\/open-source-convergence\/encryption\/us-government-fines-intels-wind-river-over-crypto-exports.php","title":{"rendered":"US government fines Intel&#8217;s Wind River over crypto exports"},"content":{"rendered":"<p><p>        Top 5 reasons to deploy VMware with Tegile  <\/p>\n<p>    The US Government has imposed a $750,000 fine on an Intel    subsidiary for exporting encryption to China, Russia, Israel    and other countries  <\/p>\n<p>    Wind River Systems was fined for exporting products that    incorporated encryption to foreign governments and to    organisations on the US government restricted list. The    controversial move means the US Department of Commerce appears    to be coming down heavily against the export of encryption even    in cases where no export to sworn enemies of the US (Iran, Cuba    and North Korea etc.) is involved.  <\/p>\n<p>    The Intel subsidiary was fined for falling to get Department of    Commerce licenses for a modest piece of business, valued at    under $3m. As such the fine represents a slap on the wrist, but    it's still a clear signal that priorities are changing.  <\/p>\n<p>    Previously self-reported cases of crypto export used to be    handled by a warning only. Multinational commercial law firm    Goodwin Procter     warned its clients to treat what happened to Wind River as    the new normal.  <\/p>\n<p>      We believe this to be the first penalty BIS has ever issued      for the unlicensed export of encryption software that did not      also involve comprehensively sanctioned countries (e.g.,      Cuba, Iran, North Korea, Sudan or Syria). This suggests a      fundamental change in BISs treatment of violations of the      encryption regulations.    <\/p>\n<p>      Historically, BIS has resolved voluntarily disclosed      violations of the encryption regulations with a warning      letter but no material consequence, and has shown itself      unlikely to pursue such violations that were not disclosed.      This fine dramatically increases the compliance stakes for      software companies  a message that BIS seemed intent upon      making in its announcement.    <\/p>\n<p>    Senior FBI and US government law officers have repeatedly    complained over recent weeks about plans by Apple and Google to    incorporate enhanced security into smartphones. Now, as    Techdirt     notes, the conflict between government regulation and the    tech industry is moving onto the renal original turf of the    first crypto wars of the late 90s - the export of strong    encryption.  <\/p>\n<p>    Strong cryptography was classified as a weapon and subject to    export controls back in the 90s. This approach fell into    disfavour for several good reasons that are even more relevant    today than they were 20 years ago.  <\/p>\n<p>    Firstly cryptography is essentially applied mathematics and the    knowledge is already out there. Secondly decent cryptography is    a fundamental component of any computing system that aspires to    be secure.  <\/p>\n<p><!-- Auto Generated --><\/p>\n<p>Originally posted here:<br \/>\n<a target=\"_blank\" href=\"http:\/\/go.theregister.com\/feed\/www.theregister.co.uk\/2014\/10\/17\/intel_subsidiary_crypto_export_fine\" title=\"US government fines Intel's Wind River over crypto exports\">US government fines Intel's Wind River over crypto exports<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p> Top 5 reasons to deploy VMware with Tegile The US Government has imposed a $750,000 fine on an Intel subsidiary for exporting encryption to China, Russia, Israel and other countries Wind River Systems was fined for exporting products that incorporated encryption to foreign governments and to organisations on the US government restricted list. <\/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-26816","post","type-post","status-publish","format-standard","hentry","category-encryption"],"_links":{"self":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/26816"}],"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=26816"}],"version-history":[{"count":0,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/posts\/26816\/revisions"}],"wp:attachment":[{"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/media?parent=26816"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/categories?post=26816"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/euvolution.com\/open-source-convergence\/wp-json\/wp\/v2\/tags?post=26816"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}