Device service controls: verify principal authority before dispatch

Aperta
  • Qualcosa non va?
#483 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
38/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
authorization, backend, security

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
Rust
Stelle
6
Fork
2
Merge medio
1g 3h
PR unite (30g)
42

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

Tutte le issue di elastos/elastos-runtime

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.