lowRISC / lowRISC/opentitan

[rom_ext] Audit hardening measure in ROM_EXT

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

Description

### Description

Audit the ROM_EXT code and evaluate the use of hardening measures.
- Identify places where additional hardening is needed (e.g. ownership transfer, rescue, etc).
- Identify places where hardening is superfluous (e.g. anything that is an output from a crypto operation probably doesn't need additional hardening).

Contributor guide

Open the contributing guide

Research direction

Start by surveying the ROM_EXT code, then trace the ownership-transfer and rescue paths called out in the issue. Review how crypto-operation outputs are handled and record where hardening is needed or unnecessary. Done means the audit has produced a justified set of findings and recommendations.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.