Describe module signing and relationship to Secure Boot

[kernel-news-talk.git] / index.html

diff --git a/index.html b/index.html
index 5ab2423b9eaec732ce524c347e6c543ca60aee40..0713e46dc51e7ecbed681ca474caab347220e72d 100644 (file)
--- a/index.html
+++ b/index.html
@@ -143,6 +143,46 @@
   </ul>
 </div>
 
+<div class="slide">
+  <h1>New KMS drivers [3.3-3.10]</h1>
+  <ul class="incremental">
+    <li>
+      DRM/KMS drivers added for old, new and virtual hardware -
+      AST, DisplayLink, Hyper-V, Matrox G200, QEMU Cirrus
+    </li>
+    <li>
+      Should be more robust than purely user-mode drivers, and
+      compatible with Secure Boot
+    </li>
+    <li>
+      Current X drivers don't work with these, so the kernel drivers
+      are disabled for now
+    </li>
+    <li>
+      Want to make it work?  Join the X Strike Force and package the
+      new X drivers
+    </li>
+  </ul>
+</div>
+
+<div class="slide">
+  <h1>Module signing [3.7]</h1>
+  <ul class="incremental">
+    <li>
+      Kernel modules can be signed at build time, and the kernel
+      configured to refuse loading unsigned modules
+    </li>
+    <li>
+      Necessary but not sufficient to implement Secure Boot -
+      we would also need signed kernel images and some other
+      restrictions when booted in this mode
+    </li>
+    <li>
+      Want to make Secure Boot work?  Come to the meeting on Tuesday
+    </li>
+  </ul>
+</div>
+
 <div class="slide">
   <h1>Questions?</h1>
 </div>