<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:foaf="http://xmlns.com/foaf/0.1/" xmlns:og="http://ogp.me/ns#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:schema="http://schema.org/" xmlns:sioc="http://rdfs.org/sioc/ns#" xmlns:sioct="http://rdfs.org/sioc/types#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" version="2.0" xml:base="https://www.linuxjournal.com/">
  <channel>
    <title>Heads</title>
    <link>https://www.linuxjournal.com/</link>
    <description/>
    <language>en</language>
    
    <item>
  <title>Tamper-Evident Boot with Heads</title>
  <link>https://www.linuxjournal.com/content/tamper-evident-boot-heads</link>
  <description>  &lt;div data-history-node-id="1340426" class="layout layout--onecol"&gt;
    &lt;div class="layout__region layout__region--content"&gt;
      
            &lt;div class="field field--name-node-author field--type-ds field--label-hidden field--item"&gt;by &lt;a title="View user profile." href="https://www.linuxjournal.com/users/kyle-rankin" lang="" about="https://www.linuxjournal.com/users/kyle-rankin" typeof="schema:Person" property="schema:name" datatype="" xml:lang=""&gt;Kyle Rankin&lt;/a&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-body field--type-text-with-summary field--label-hidden field--item"&gt;&lt;p&gt;&lt;em&gt;Learn about how the cutting-edge, free software Heads project detects
BIOS and kernel tampering, all with keys under your control.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;
&lt;em&gt;Disclaimer:&lt;/em&gt; I work for Purism, and my experience with Heads began
as part of supporting it on Purism's hardware. As a technical writer,
I personally find ads that mask themselves as articles in technical
publications disingenuous, and this article &lt;em&gt;in no way&lt;/em&gt; is intended to be
an advertisement for my employer. However, in writing this deep dive piece, I
found that mentioning Purism was unavoidable in some places
without leaving out important information about Heads—in particular,
the list of overall supported hardware and an explanation of Heads'
HOTP alternative to TOTP authentication, because it requires a specific
piece Purism hardware.
&lt;/p&gt;

&lt;p&gt;
Some of the earliest computer viruses attacked the boot sector—that bit
of code at the beginning of the hard drive in the Master Boot Record
that allowed you to boot into your operating system. The reasons for this have
to do with stealth and persistence. Viruses on the filesystem itself
would be erased if users re-installed their operating systems, but
if they didn't erase the boot sector as part of the re-install process,
boot sector viruses could stick around and re-infect the operating system.
&lt;/p&gt;

&lt;p&gt;
Antivirus software vendors ultimately added the ability to scan the boot sector
for known viruses, so the problem was solved, right? Unfortunately, as computers,
operating systems and BIOSes became more sophisticated, so did the boot-sector attacks. Modern attacks take over before the OS is launched and
infect the OS itself, so when you try to search for the attack through
the OS, the OS tells you everything is okay.
&lt;/p&gt;

&lt;p&gt;
That's not to say modern defenses to this type of
attack don't exist. Most modern approaches involve proprietary software that locks
down the system so that it can boot only code that's signed by a vendor
(typically Microsoft, Apple, Google or one of their approved third-party
vendors). The downside, besides the proprietary nature of this defense,
is that you are beholden to the vendor to bless whatever code you want
to run, or else you have to disable this security feature completely (if you can).
&lt;/p&gt;

&lt;p&gt;
Fortunately, an alternative exists that is not only free software, but
that also takes a completely different approach to boot security by alerting
you to tampering instead of blocking untrusted code. This approach,
Heads, can detect tampering not only in the BIOS itself but also in
all of your important boot files in the /boot directory, including the
kernel, initrd and even your grub config. The result is a trusted boot
environment with keys fully under your own control.
&lt;/p&gt;

&lt;p&gt;
In this article,
I describe some of the existing boot security approaches in more
detail, along with some of their limitations, and then I describe how Heads
works, and how to build and install it on your own system.
&lt;/p&gt;&lt;/div&gt;
      
            &lt;div class="field field--name-node-link field--type-ds field--label-hidden field--item"&gt;  &lt;a href="https://www.linuxjournal.com/content/tamper-evident-boot-heads" hreflang="en"&gt;Go to Full Article&lt;/a&gt;
&lt;/div&gt;
      
    &lt;/div&gt;
  &lt;/div&gt;

</description>
  <pubDate>Thu, 31 Jan 2019 14:08:08 +0000</pubDate>
    <dc:creator>Kyle Rankin</dc:creator>
    <guid isPermaLink="false">1340426 at https://www.linuxjournal.com</guid>
    </item>

  </channel>
</rss>
