<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Hardening on Rootcommit WIP</title>
    <link>https://rootcommit.l0g.eu/tags/hardening/</link>
    <description>Recent content in Hardening on Rootcommit WIP</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 15 Apr 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://rootcommit.l0g.eu/tags/hardening/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>U-Boot: protect sensitive environment variables</title>
      <link>https://rootcommit.l0g.eu/2026/u-boot-protect-sensitive-environment-variables/</link>
      <pubDate>Wed, 15 Apr 2026 00:00:00 +0000</pubDate>
      <guid>https://rootcommit.l0g.eu/2026/u-boot-protect-sensitive-environment-variables/</guid>
      <description>&lt;p&gt;This is a follow-up from our &lt;a href=&#34;https://rootcommit.l0g.eu/2026/accessing-u-boot-env-from-c/&#34;&gt;Accessing the U-Boot environment from a C program&lt;/a&gt; blog post.&lt;/p&gt;&#xA;&lt;h3 id=&#34;need-to-protect-the-environment&#34;&gt;🌳Need to protect the environment&lt;/h3&gt;&#xA;&lt;p&gt;When you&amp;rsquo;re trying to harden an embedded Linux device to make it more resistant to attacks, one key part to secure is the bootloader, because that&amp;rsquo;s the part that boots the operating system. Even you implement a &lt;strong&gt;secure boot&lt;/strong&gt; chain, if an attacker manages to interrupt the boot process and get access to the bootloader shell, this attacker would be able to load and run her/his own payload on the device.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Yocto security: Kernel Hardening</title>
      <link>https://rootcommit.l0g.eu/2025/yocto-security-kernel-hardening/</link>
      <pubDate>Tue, 07 Oct 2025 00:00:00 +0000</pubDate>
      <guid>https://rootcommit.l0g.eu/2025/yocto-security-kernel-hardening/</guid>
      <description>&lt;p&gt;This is another blog post about securing your Yocto built systems:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://rootcommit.l0g.eu/2025/securing-yocto-built-systems/&#34;&gt;Securing Yocto Built Systems overview presentation slides&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://rootcommit.l0g.eu/2025/yocto-security-production-and-development-images/&#34;&gt;Yocto Security: Production and Development Images&lt;/a&gt;&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;a href=&#34;https://rootcommit.l0g.eu/2025/yocto-security-kernel-hardening/&#34;&gt;Yocto security: Kernel Hardening&lt;/a&gt; ⬅️&lt;/p&gt;&#xA;&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;The Linux kernel is the cornerstone and stronghold of a Linux based system. Unlike user-space applications which run with limited privileges, if it&amp;rsquo;s compromised, there is almost no limit to what an attacker can do.&lt;/p&gt;&#xA;&lt;p&gt;While nothing is unbreakable, there are two types of settings you can change to make your kernel harder to compromise:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
