Skip to content

Comments

optionally verify TcbEvaluationDataNumber#5

Merged
burgerdev merged 1 commit intomainfrom
evalnum
Jan 20, 2026
Merged

optionally verify TcbEvaluationDataNumber#5
burgerdev merged 1 commit intomainfrom
evalnum

Conversation

@burgerdev
Copy link
Member

No description provided.

@burgerdev burgerdev requested a review from thomasten January 15, 2026 10:02
verify/verify.go Outdated
logger.V(2).Info("Getting TCB Info: ", tcbInfoURL)
header, body, err := trust.GetWith(ctx, getter, tcbInfoURL)
if err != nil {
// TODO(burgerdev): 410 means evaluationDataNumber is too old, maybe just query without it?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

May be obvious, but to summarize:

  • Security-wise fine as long as the check below is there
  • May improve availability
  • May hide errors

Both options are fine with me. I don't have a preference what to do here.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

After revisiting the code, I found that the HTTPSGetter interface does not forward HTTP status codes. Since it's a simple change on the caller side to update the expected number, whereas it's complicated to check here (forwarding the errors, and the error hiding you observed), I'm going to keep it as-is.

@burgerdev burgerdev force-pushed the evalnum branch 2 times, most recently from c06f090 to 612f055 Compare January 20, 2026 14:06
Signed-off-by: Markus Rudy <mr@edgeless.systems>
@burgerdev
Copy link
Member Author

I simplified the code a bit, but the behaviour remains the same as in the original commit.

@burgerdev burgerdev merged commit ac8c4b4 into main Jan 20, 2026
5 checks passed
@burgerdev burgerdev deleted the evalnum branch January 20, 2026 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants