From: Demi Marie Obenour <demiobenour@gmail.com>
To: devel@spectrum-os.org
Subject: Verified boot and filesystem choices
Date: Fri, 13 Jun 2025 21:24:14 -0400 [thread overview]
Message-ID: <38bffd12-26ba-47cb-a425-1326e3400c8b@gmail.com> (raw)
[-- Attachment #1.1.1: Type: text/plain, Size: 1112 bytes --]
Bcachefs is not very stable right now, and BTRFS is not a good choice
from a verified boot perspective. f2fs is what is used in Android
and ext4 is used in Chromebooks, so they at least have the backing of
Google's security team when it comes to vulnerabilities involving
maliciously crafted filesystem images. BTRFS doesn't.
The reason this matters for Spectrum is that verified boot aims to
prevent system compromise from persisting across reboots, and an
attacker who has compromised a Spectrum system can craft whatever
image they want on the writable volume.
Would it make sense to use f2fs or ext4? That means no reflinks
and no snapshots, which would be annoying at least. Another option
might be to use FUSE for the writable volume, with kernel filesystems
only used for the (signed and dm-verity protected) root volume.
This is the only option supported by Linux's upstream maintainers,
who (with the notable exception of Kent Overstreet) appear to have
no interest in hardening filesystems against maliciously crafted
images.
--
Sincerely,
Demi Marie Obenour (she/her/hers)
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 7253 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2025-06-14 1:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-14 1:24 Demi Marie Obenour [this message]
2025-06-14 8:23 ` Verified boot and filesystem choices Alyssa Ross
2025-06-14 21:32 ` Demi Marie Obenour
2025-06-15 9:13 ` Alyssa Ross
2025-06-15 16:00 ` Demi Marie Obenour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=38bffd12-26ba-47cb-a425-1326e3400c8b@gmail.com \
--to=demiobenour@gmail.com \
--cc=devel@spectrum-os.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).