Repository navigation
Add a reference for TPM-sealed /var on Jetson - #29
Merged
Merged
Conversation
There is no security-flavoured reference in this repo, and hardware-backed /var encryption is the feature customers ask about first on Jetson. A reference is the right shape for it because the whole feature is three lines of avocado.yaml: someone who can run `avocado init --reference` gets a working project, where a prose guide leaves them transcribing config. Pin the 2026 release rather than the 2024 every other reference uses. cryptsetup-var is not published on 2024 at all, so this cannot be demonstrated there; a 2024 project fails inside `avocado install` with an error naming no missing package, which is why the README and the guide both lead with the release. Set hardware: tpm2 rather than leaving the default. On auto, a unit whose firmware TPM did not come up still boots on a software-derived key and reports the degrade, so a fleet can be software-keyed while believing it is hardware-bound. A reference people copy should not ship the setting that fails open. Built, flashed and booted on a Jetson Orin Nano before committing: the outputs in the verify section are copied from that run rather than composed, including the luksDump PCR 7 seal and both keyslots. Signed-off-by: Javier Tia <javier@peridio.com>
Avocado References — Build Check
Totals: 1 ✅ passed · 0 ❌ failed Per-reference logs: workflow run |
nicksinas
approved these changes
Sep 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
There is no security-focused reference in this repo, and hardware-backed /var encryption is the feature customers ask about first on Jetson. The config is three lines, but nothing demonstrates it end to end.
Solution
A minimal reference whose point is the
varblock. No application code, so the config is the subject rather than an incidental detail.Key changes
jetson-encrypted-var/with avocado.yaml, README.md and getting_started.mdhardware: tpm2rather than theautodefaultReviewer notes
Two deliberate divergences worth your attention:
It pins 2026/next.
cryptsetup-varis not published on 2024 at all, so this cannot be demonstrated there. A 2024 project fails insideavocado installwith an error naming no missing package.It sets
hardware: tpm2, not the default. Onauto, a unit whose firmware TPM did not come up still boots on a software-derived key and reports the degrade, so a fleet can be software-keyed while believing it is hardware-bound. A reference people copy should not ship the setting that fails open.Built, flashed and booted on an Orin Nano before opening this. The outputs in the Verify section are copied from that run, including the luksDump PCR 7 seal and both keyslots.
Feedback I want: whether pinning 2026 here is acceptable while the rest of the repo is on 2024, and whether
jetson-encrypted-varis the right name.