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

Abierto
#246 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
30/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, shell
Área
devops, security

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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)?

Lenguaje dominante
Shell
Estrellas
26
Forks
18
Merge medio
3 d 10 h
PR fusionados (30 d)
13

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de flashbots/flashbots-images

Todos los issues de flashbots/flashbots-images

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.