Skip to content

Commit da9bb77

Browse files
author
Dongkeun Lee
committed
docs(azure): describe the sealed guest read as it actually behaves
1 parent cadca32 commit da9bb77

1 file changed

Lines changed: 4 additions & 2 deletions

File tree

bin/fm-azure-validation.py

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1688,8 +1688,10 @@ def sealed_guest_text(env, state):
16881688
the sealed artifact and is what a resumed attempt must run. The working tree
16891689
is used only when it still matches the seal, which keeps a cell whose
16901690
payload was pruned behaving exactly as before. Neither source is trusted on
1691-
provenance: only a file whose digest IS the sealed digest is ever returned,
1692-
so this widens recovery without widening what may execute.
1691+
provenance: the bytes are read ONCE, digested in memory, and those exact
1692+
bytes are what is returned, so what executes on the cell is what was
1693+
verified rather than whatever a later read would have found. This widens
1694+
recovery without widening what may execute.
16931695
"""
16941696
expected = state["request"]["protocol"]["guest_digest"]
16951697
candidates = []

0 commit comments

Comments
 (0)