<story><title>Safe and Secure Drivers in High-Level Languages [video]</title><url>https://media.ccc.de/v/35c3-9670-safe_and_secure_drivers_in_high-level_languages</url></story><parent_chain><item><author>saagarjha</author><text>Personally, I&amp;#x27;d call this writing &amp;quot;Safer and More Secure Drivers in High-Level Languages&amp;quot;, because there are still unsafe operations going on (for DMA, etc.): &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ixy-languages&amp;#x2F;ixy.swift&amp;#x2F;search?q=Unsafe&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ixy-languages&amp;#x2F;ixy.swift&amp;#x2F;search?q=Unsafe&lt;/a&gt;&lt;p&gt;While it&amp;#x27;s great that you get improved safety (and often nicer and easier to reason about code) by using something other than C, you can still have memory safety issues from cavalier or incorrect usage of unsafe APIs, since they undermine the guarantees the language provides with regards to correctness.&lt;p&gt;Also, unrelated: does anyone actually have the slides (you know, the presentation file with text in it, rather than the mp4 that CCC is offering me) for this presentation? It&amp;#x27;s really annoying to scrub through a video to find stuff on a slow internet connection :(</text></item></parent_chain><comment><author>pjmlp</author><text>Quite true, however the unsafety code coverage gets reduced quite significantly.&lt;p&gt;On the last Linux Kernel Summit, according to Google, 68% of Linux kernel security exploits are caused by C memory corruption issues due to lack of bounds checking.</text></comment>
<story><title>Safe and Secure Drivers in High-Level Languages [video]</title><url>https://media.ccc.de/v/35c3-9670-safe_and_secure_drivers_in_high-level_languages</url></story><parent_chain><item><author>saagarjha</author><text>Personally, I&amp;#x27;d call this writing &amp;quot;Safer and More Secure Drivers in High-Level Languages&amp;quot;, because there are still unsafe operations going on (for DMA, etc.): &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ixy-languages&amp;#x2F;ixy.swift&amp;#x2F;search?q=Unsafe&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ixy-languages&amp;#x2F;ixy.swift&amp;#x2F;search?q=Unsafe&lt;/a&gt;&lt;p&gt;While it&amp;#x27;s great that you get improved safety (and often nicer and easier to reason about code) by using something other than C, you can still have memory safety issues from cavalier or incorrect usage of unsafe APIs, since they undermine the guarantees the language provides with regards to correctness.&lt;p&gt;Also, unrelated: does anyone actually have the slides (you know, the presentation file with text in it, rather than the mp4 that CCC is offering me) for this presentation? It&amp;#x27;s really annoying to scrub through a video to find stuff on a slow internet connection :(</text></item></parent_chain><comment><author>emmericp</author><text>I&amp;#x27;ve added them to the git repo: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ixy-languages&amp;#x2F;ixy-languages&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;slides&amp;#x2F;35C3.pdf&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;ixy-languages&amp;#x2F;ixy-languages&amp;#x2F;blob&amp;#x2F;master&amp;#x2F;s...&lt;/a&gt;</text></comment>