lowRISC / lowRISC/opentitan

[rom_ext, ownership] Consider tracking previous owners

Open
#24,429 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

SW:ROM_EXT
Dominant language
SystemVerilog
Stars
3.6k
Forks
1.1k
Avg merge
2d 22h
Merged PRs (30d)
141

Description

Description

As part of ownership transfer, consider tracking the previous owner.

Ideas:

  1. Keep a hash of the previous owner's key.
  2. Keep a hash-chain of all previous owners:
    Upon each ownership transfer: prev_owner_hash = HASH(prev_owner_key || prev_owner_hash)

Given a list of all previous owner public keys, the prev_owner_hash could be independently verified.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue identifies the rom_ext ownership-transfer area but names no implementation files, entry points, or tests. First locate the ownership-transfer flow and its existing test coverage, then determine which previous-owner representation is intended and how independent verification should work; done means the design is agreed and its behavior is covered.

Written by the indexing model from the issue text.

Assessment

Domain
cryptography, security
Issue type
Feature
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.