Device service controls: verify principal authority before dispatch

Aberta
  • Algo errado?
#483 2 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
38/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
rust
Domínio
authorization, backend, security

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Rust
Estrelas
6
Forks
2
Merge médio
1d 3h
PRs com merge (30d)
42

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de elastos/elastos-runtime

Todas as issues de elastos/elastos-runtime

Issues semelhantes

Mais issues de Rust

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.