Hacktoberfest 2026：维护者为十月标记出来的 issue，仍然开放、适合新手。 浏览 Hacktoberfest issue

Support Tails OS with persistent storage, firmware verification and Tails system verification

未关闭
  • 哪里不对？
#2,218 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
linux
领域
operating-systems, security

调研方向

Start by reading the related Heads issues #1260, #1480, #1651, and #1873, plus the discussion in pull request #2153; the issue does not identify specific files or tests. Compare the two proposed Tails USB approaches, including how Heads verifies firmware and the Tails system partition and stores the HOTP counter and primary handle hash. Done means agreeing on a viable approach and implementing support for Tails persistent storage and system verification without verifying its changing storage partition.

由索引模型根据 Issue 内容生成。

描述

I would like to boot a Tails OS USB drive from Heads with

  • a) Tails persistent storage
  • b) TOTP/HOTP verification of Heads firmware
  • c) and verification of the Tails system partition (no separate /boot partition).

Verification of the persistent storage partition on the USB drive is a non-goal as it will change during each usage.

As dual boot seems another complex story (https://tails.net/support/faq/index.en.html#permanent-install) let’s reduce it to Tails only without an internal hard drive.

Regarding Tails there are two options:

  1. Putting ISO + detached signature on a USB drive and create or mimic a persistent storage to achieve a) and c). TOTP/HOTP verification would have to become independent of a /boot partition to achieve b).
  2. Regular installation of Tails on a USB drive with persistent storage and treating it like an internal drive during Heads boot to store and find the primary handle hash, the HOTP counter, hashes signature etc.

In case 1. it is currently not possible to just load the ISO and create a persistent storage. I didn’t manage to manually create/copy an existing persistent storage and open it either.
Thus we would have to find a hack to create and open a persistent storage when booting from a verified Tails ISO. Anyway, we would still have to find a place to store the primary handle hash and the HOTP counter. Maybe in the TPM? (https://github.com/linuxboot/heads/issues/1260)

In case 2. we would need Heads to treat an external drive as an internal one as discussed here https://github.com/linuxboot/heads/issues/1873#issuecomment-2540552084. But even then Tails installed writing e.g. an .img file with dd does not have a separate /boot partition. Also, I have not yet tested how Tails reacts to storing extra kexec_*.txt files under / in the system partition.
2. has the advantage that the Tails USB would be completely bootable from a non-Heads machine, which is currently not the case with a USB that contains an ISO and a detached signature, but is not bootable.

Why does Heads actually expect a separate /boot partition? Would it be an option to write all the kexec_*.txt files on the system partition? This partition by design should not change barring Tails updates.

I considered installing Tails on an internal drive but the FAQ discourages it:
https://tails.net/support/faq/index.en.html#permanent-install

I am motivated to put work into this, incl. Into the related issues such as getting rid of the dependency of TOTP/HOTP verification on a /boot partition.

Before I get started I would like to get some feedback and ideas on what seems to be the most promising approach.

主要语言
Makefile
星标
1.6k
派生
211
平均合并
2 天 11 小时
30 天内合并 PR
6

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

linuxboot/heads 的其他 Issue

查看 linuxboot/heads 的全部 Issue

相似的 Issue

更多 Operating Systems Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。