GCP: pinning only RTMR1/RTMR2 with an endorsed MRTD (and is flashbots-images' measure-gcp still used?)

Aperta
#246 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
30/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
github, shell
Ambito
devops, security

Direzione di ricerca

Start by tracing make measure-gcp, scripts/gcp_measurements_to_dcap.sh, and the CI and documentation references to determine whether the GCP measurement path is still used. Then review the linked attested-tls proposal and how GCP TDX evidence verifies MRTD; the issue is done when the maintainers decide whether to upstream that safety change and how to handle direct attest measure gcp output.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

At Seismic we admit GCP TDX guests by pinning RTMR1 and RTMR2, while still requiring MRTD to be a firmware build Google has endorsed (like you guys do in your portable measurement policies). We'd like to compute those values with attest measure gcp instead of maintaining our own predictor. Two questions:

1. Is anyone still using make measure-gcp in flashbots-images?

It runs dstack-mr (flashbots/dstack-mr-gcp), whose only consumer is scripts/gcp_measurements_to_dcap.sh. CI and the docs only use measure-portable / measure-portable-gcp. dstack-mr models RTMR2 as the command line plus initrd only, so it probably doesn't match UKIs built with systemd-stub ≥ 256, which also measures each section. If nobody uses it, happy to open a PR removing measure-gcp, the reshape script and the dstack-mr-gcp flake input.

2. Would you take the changes that make RTMR1/RTMR2-only GCP policies safe in attested-tls?

kind: dcap output is rejected (UnsafeAttestMeasureDcapOutput) because MRTD would go unchecked, which makes sense. But an explicit gcp-tdx record that pins only rtmr1/rtmr2 is accepted today and has the same gap. What we'd propose:

  1. Verify Google's endorsement of MRTD for every gcp-tdx evidence, not only inside the portable comparison, and record it with the evidence so archived verification can re-check it. We run this in our fork (https://github.com/SeismicSystems/attested-tls/pull/7), happy to clean it up and upstream it if you guys agree with this approach.
  2. With (1) in place, document gcp-tdx records pinning only rtmr1/rtmr2 as safe. They already parse.
  3. Optionally, accept attest measure gcp output directly. That needs attest to say which platform the output is for, since measure gcp and measure self-hosted both emit kind: dcap (an attestation_type field would do). attested-tls could then map it to a gcp-tdx record.

Would you take (1)? Any preference on (3)?

Lingua principale
Shell
Stelle
26
Fork
18
Merge medio
3g 10h
PR unite (30g)
13

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di flashbots/flashbots-images

Tutte le issue di flashbots/flashbots-images

Issue simili

Altre issue su Shell/Bash

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.