<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>http://kernsec.org/wiki/index.php?action=history&amp;feed=atom&amp;title=Linux_Security_Summit_2014%2FAbstracts%2FCook_1</id>
	<title>Linux Security Summit 2014/Abstracts/Cook 1 - Revision history</title>
	<link rel="self" type="application/atom+xml" href="http://kernsec.org/wiki/index.php?action=history&amp;feed=atom&amp;title=Linux_Security_Summit_2014%2FAbstracts%2FCook_1"/>
	<link rel="alternate" type="text/html" href="http://kernsec.org/wiki/index.php?title=Linux_Security_Summit_2014/Abstracts/Cook_1&amp;action=history"/>
	<updated>2026-05-07T12:04:20Z</updated>
	<subtitle>Revision history for this page on the wiki</subtitle>
	<generator>MediaWiki 1.36.1</generator>
	<entry>
		<id>http://kernsec.org/wiki/index.php?title=Linux_Security_Summit_2014/Abstracts/Cook_1&amp;diff=3504&amp;oldid=prev</id>
		<title>JamesMorris at 16:01, 15 July 2014</title>
		<link rel="alternate" type="text/html" href="http://kernsec.org/wiki/index.php?title=Linux_Security_Summit_2014/Abstracts/Cook_1&amp;diff=3504&amp;oldid=prev"/>
		<updated>2014-07-15T16:01:23Z</updated>

		<summary type="html">&lt;p&gt;&lt;/p&gt;
&lt;table style=&quot;background-color: #fff; color: #202122;&quot; data-mw=&quot;interface&quot;&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;col class=&quot;diff-marker&quot; /&gt;
				&lt;col class=&quot;diff-content&quot; /&gt;
				&lt;tr class=&quot;diff-title&quot; lang=&quot;en&quot;&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;← Older revision&lt;/td&gt;
				&lt;td colspan=&quot;2&quot; style=&quot;background-color: #fff; color: #202122; text-align: center;&quot;&gt;Revision as of 16:01, 15 July 2014&lt;/td&gt;
				&lt;/tr&gt;&lt;tr&gt;&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot; id=&quot;mw-diff-left-l5&quot;&gt;Line 5:&lt;/td&gt;
&lt;td colspan=&quot;2&quot; class=&quot;diff-lineno&quot;&gt;Line 5:&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;== Presenter ==&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;== Presenter ==&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br/&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br/&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;−&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #ffe49c; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;Kees Cook&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot; data-marker=&quot;+&quot;&gt;&lt;/td&gt;&lt;td style=&quot;color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #a3d3ff; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;Kees Cook&lt;ins style=&quot;font-weight: bold; text-decoration: none;&quot;&gt;, Google&lt;/ins&gt;&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br/&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;br/&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;tr&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;== Abstract ==&lt;/div&gt;&lt;/td&gt;&lt;td class=&quot;diff-marker&quot;&gt;&lt;/td&gt;&lt;td style=&quot;background-color: #f8f9fa; color: #202122; font-size: 88%; border-style: solid; border-width: 1px 1px 1px 4px; border-radius: 0.33em; border-color: #eaecf0; vertical-align: top; white-space: pre-wrap;&quot;&gt;&lt;div&gt;== Abstract ==&lt;/div&gt;&lt;/td&gt;&lt;/tr&gt;
&lt;/table&gt;</summary>
		<author><name>JamesMorris</name></author>
	</entry>
	<entry>
		<id>http://kernsec.org/wiki/index.php?title=Linux_Security_Summit_2014/Abstracts/Cook_1&amp;diff=3501&amp;oldid=prev</id>
		<title>JamesMorris: New page: == Title ==  Verified Component Firmware  == Presenter ==  Kees Cook  == Abstract ==  Privileged executable code running on a device is not limited to just the Boot Firmware and Kernel. On...</title>
		<link rel="alternate" type="text/html" href="http://kernsec.org/wiki/index.php?title=Linux_Security_Summit_2014/Abstracts/Cook_1&amp;diff=3501&amp;oldid=prev"/>
		<updated>2014-07-15T15:51:07Z</updated>

		<summary type="html">&lt;p&gt;New page: == Title ==  Verified Component Firmware  == Presenter ==  Kees Cook  == Abstract ==  Privileged executable code running on a device is not limited to just the Boot Firmware and Kernel. On...&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;== Title ==&lt;br /&gt;
&lt;br /&gt;
Verified Component Firmware&lt;br /&gt;
&lt;br /&gt;
== Presenter ==&lt;br /&gt;
&lt;br /&gt;
Kees Cook&lt;br /&gt;
&lt;br /&gt;
== Abstract ==&lt;br /&gt;
&lt;br /&gt;
Privileged executable code running on a device is not limited to&lt;br /&gt;
just the Boot Firmware and Kernel. One major area that gets frequently&lt;br /&gt;
overlooked is Component Firmware: firmware loaded on network interfaces,&lt;br /&gt;
wifi and cellular wireless devices, hard drives, keyboards, etc. Some&lt;br /&gt;
of these devices have direct DMA access to system physical memory, some&lt;br /&gt;
have access to potentially sensitive information (keystrokes, network&lt;br /&gt;
or storage data, etc). Presently, the Linux Kernel loads firmware from&lt;br /&gt;
userspace via directly located files, data passed by uevent handlers, or&lt;br /&gt;
by specialized updater tools that manipulate (potentially undocumented)&lt;br /&gt;
device interfaces. There is no mechanism in place for the kernel to&lt;br /&gt;
reason about the origin of the firmware, so it is possible for userspace&lt;br /&gt;
to load malicious Component Firmware that could result in a compromised&lt;br /&gt;
kernel or a component that persistently snoops on data.&lt;br /&gt;
&lt;br /&gt;
As was done for kernel module loading, I have introduced a new interface&lt;br /&gt;
for firmware loading that operates on a file descriptor rather than&lt;br /&gt;
arbitrary blobs passed from userspace. This allows a system to limit&lt;br /&gt;
firmware loading to only known sources. For example, firmware loading&lt;br /&gt;
could be limited to read-only crypto-verified storage, or with verified&lt;br /&gt;
signatures.&lt;br /&gt;
&lt;br /&gt;
Additionally, I will present a methodology for evaluating Component&lt;br /&gt;
Firmware risks based on the component's own level of firmware validation&lt;br /&gt;
and the component's access to sensitive interfaces or data. With this,&lt;br /&gt;
a plan for firmware that is loaded external to the kernel (entirely&lt;br /&gt;
via userspace) can be developed, potentially leading to filtered device&lt;br /&gt;
communication.&lt;/div&gt;</summary>
		<author><name>JamesMorris</name></author>
	</entry>
</feed>