Support Tails OS with persistent storage, firmware verification and Tails system verification
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 35/100
- issue の種類
- 機能追加
- 明瞭さ
- 説明が足りない
- 活発さ
- 活発
- 技術スタック
- linux
調査の方向性
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:
- 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).
- 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.
- https://github.com/linuxboot/heads/issues/1651
- https://github.com/linuxboot/heads/pull/2153
- https://github.com/linuxboot/heads/issues/1480
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時間
- マージ済み PR（30日）
- 6
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
linuxboot/heads のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 86/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 90/100
-
難易度 1/5 1時間未満 初心者へのやさしさ 65/100
-
難易度 2/5 1〜3時間 初心者へのやさしさ 64/100
-
help wanted security SMM upstream
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
linuxboot/heads の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 67/100
void-linux/void-runit#141 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
ARM-software/sysarch-acs#600 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
A SKILL.md larger than max_skill_size is read whole through the mount対応中かも @Frun1na が 1 日前に担当しました。 オープンcomponent:skillfs
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
agentic-os-org/ANOLISA#6060 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
-
[IO_URING] Unregistered write requires a mutable buffer対応中かも @rksharma-owg が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 70/100
apple/swift-system#400 ·
メンテナーはふだん 1 日以内に返信