Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

TC comment for sharing of physical media

Abierto
  • ¿Algo no está bien?
#80 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Documentación
Claridad
Necesita aclaración
Estado de actividad
Estancado
Área
documentation

Línea de trabajo

Start with the TC comment and the editor note, then review FDP_VMS_EXT.1 and FDP_RIP_EXT.2 in the protection profile. Determine whether the proposed warning or data-sharing requirement belongs in a future version; done would mean an agreed specification change, not just further discussion.

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

Descripción

Comment from TC:

5.1.7 Protection of the TSF (FPT) / FPT_RDM_EXT.1 Removable Devices and Media / FPT_RDM_EXT.1.2

  Care has been taken to specify the dangers of sharing removable media between domains.  How about a physical device like a hard disk that is passed through knowingly to 2 separate VMs.  Should there be something like a warning on VM launch that the HD is available to another VM (that may not be currently powered up)?  Definitely sounds problematic to implement though.  I am suggesting it because it presents the same issues that removable media does.

NIAP response: this will be addressed in a future version.

Editor note:

I think this is partially covered by FDP_VMS_EXT.1. FDP_VMS_EXT.1.4 says that data can only be read or transferred to or from another Guest VM except for either virtual networking or some other mechanism explicitly specified by the ST author. You could look at this as prohibiting two Guest VMs from being able to read the same physical storage unless the ST specifically defines what you're describing here as a way to do that. 

And then FDP_RIP_EXT.2 requires clearing of physical disk storage when being allocated to a Guest VM, specifically to prevent a case where a Guest VM has access to storage previously used by a different one.

For the future I would suggest tacking on another element to FDP_VMS_EXT.1 where we have the ST author specify what, if any, warnings or other mechanisms the TOE has to indicate when data sharing is allowed.
Lenguaje dominante
Makefile
Estrellas
3
Forks
0
Sin PR fusionados en 30 d

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 commoncriteria/virtualization

Todos los issues de commoncriteria/virtualization

Issues similares

Más issues de Documentation

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.