lowRISC / lowRISC/opentitan

[Perso] Update perso TLV definitions from OpenTitan Provisioning repo

Open
#29,432 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

### Description

In OpenTitan provisioning PR https://github.com/lowRISC/opentitan-provisioning/pull/293 we added new perso blob TLV header which allows for larger TLV data fields to accommodate larger key sizes for PQ algorithms.

In OT provisioning repo we have defined new version TLV to indicate when to switch between the existing 16bit TLV header and the extended 32bit header size. We should bring in the new TLV definitions from the OT provisioning repo once merged.

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

Review the existing perso TLV definitions in OpenTitan alongside opentitan-provisioning PR #293. Confirm the upstream PR is merged, then bring over the new version TLV and extended 32-bit header definitions; done means OpenTitan reflects the provisioning repository's definitions for switching between 16-bit and 32-bit headers.

Written by the indexing model from the issue text.

Assessment

Domain
embedded-iot, security
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.