Device service controls: verify principal authority before dispatch

Abierto
  • ¿Algo no está bien?
#483 2 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
38/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
authorization, backend, security

Línea de trabajo

Read the shared device service control operation at the stated develop and candidate revisions, then trace how human, app, and agent entry points reach dispatch. The issue does not identify paths or configuration conditions; begin by locating that operation and its existing tests. Done means the owner policy is enforced before dispatch, isolated tests show zero effects for disallowed or revoked principals and success for the approved path, and independent review records release impact.

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

Descripción

Intended behavior

Runtime applies the approved principal-role policy to device-level service controls before it dispatches an effect. Human, app and agent entry points receive the same decision. Status reads can have a separately defined policy.

The #93 audit found a source-level authority question that needs verification before release triage. Detailed paths and configuration conditions are retained in the private audit evidence. This public issue deliberately records only the required contract and proof. Installed reachability and impact are unverified.

Source boundary: develop 3beb816438fd567145a8d725e22465bd83277cf0 and local candidate 460b1888d344f52cebd1c25866be88ff4085f035. The candidate contains the same relevant path.

Acceptance

  • The owner states which principals may change the device service state.
  • Runtime enforces that policy in the shared operation before dispatch.
  • An isolated fixture records zero effects for disallowed and revoked principals.
  • The approved owner path succeeds with the required proof.
  • Human and agent entry points receive equivalent decisions.
  • Independent security review records the candidate and whether this blocks 0.8.0 or has an explicitly accepted restricted scope.

Related: #178 and #464 own the broader approval/policy work. This issue owns the narrow verification from the current release audit. It starts no live-host testing or configuration change.

Lenguaje dominante
Rust
Estrellas
6
Forks
2
Merge medio
1 d 3 h
PR fusionados (30 d)
42

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 elastos/elastos-runtime

Todos los issues de elastos/elastos-runtime

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.