<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>secure-boot on TODO: Document</title>
    <link>https://ryan.lovelett.me/tags/secure-boot/</link>
    <description>Recent content in secure-boot on TODO: Document</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 17 Jun 2026 14:13:00 +0000</lastBuildDate><atom:link href="https://ryan.lovelett.me/tags/secure-boot/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Secure Boot ZFSBootMenu with Custom Keys and Redundant ESPs</title>
      <link>https://ryan.lovelett.me/posts/2026-06-17-secure-boot-zfsbootmenu-sbctl/</link>
      <pubDate>Wed, 17 Jun 2026 14:13:00 +0000</pubDate>
      
      <guid>https://ryan.lovelett.me/posts/2026-06-17-secure-boot-zfsbootmenu-sbctl/</guid>
      <description>If you run Arch Linux on a mirrored ZFS root pool, you likely have redundant EFI System Partitions (ESPs) mapped to multiple NVMe drives for resilience.
However, protecting this boot path with Secure Boot can be a challenge. With the use of Secure Boot key manager you can take ownership of your motherboard&amp;rsquo;s platform security, automat syncing across multiple drives, and verify the integrity of your native ZFS boot environment.</description>
    </item>
    
  </channel>
</rss>
