lowRISC / lowRISC/opentitan

[rom_ext] Add an update_policy to the ownership block, allowing the owner to specify how ownership updates should be performed

Open
#24,657 0 comments 0 reactions 0 assignees View on GitHub
Priority:P1 SW:ROM_EXT Type:Task
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

Examples:
- Full unlock allowed.
- Unlock to Self only.
- Accept signed updates from Self if config_version is greater.

Contributor guide

Open the contributing guide

Research direction

The issue identifies the rom_ext ownership block but no files or tests. Start by locating that block and its existing update handling, then clarify how the three listed policies should behave and how policy configuration is represented. Done means the ownership block supports the agreed update policies with coverage for each example.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.