Device service controls: verify principal authority before dispatch
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 38/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- rust
- 領域
- authorization, backend, security
研究方向
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.
由索引模型根據 Issue 內容生成。
描述
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.
- 主要語言
- Rust
- 星號
- 6
- 分支
- 2
- 平均合併
- 1 天 3 小時
- 30 天內合併 PR
- 42
環境準備
這個專案沒有提供開發容器、Dockerfile 或貢獻指南，環境需要你自己搭建：先看它的 README，通用步驟見我們的新手貢獻指南。
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
elastos/elastos-runtime 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 72/100
elastos/elastos-runtime#563 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 76/100
elastos/elastos-runtime#508 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
elastos/elastos-runtime#436 · 1 則留言 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
elastos/elastos-runtime#427 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
elastos/elastos-runtime#405 ·
維護者通常 1 天內回覆
查看 elastos/elastos-runtime 的全部 Issue
相似的 Issue
-
難度 1/5 1 小時以內 新手友好度 94/100
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 65/100
維護者通常 2 天內回覆
-
ci enhancement need-triage
難度 2/5 1-3 小時 新手友好度 86/100
維護者通常 1 天內回覆
-
enhancement good first issue help wanted
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 1 天內回覆
-
area:ui
難度 2/5 1-3 小時 新手友好度 78/100
openfootmanager/openfootmanager#1365 ·
維護者通常 1 天內回覆