lowRISC / lowRISC/ibex

[rtl] Declare Zkt - Scalar crypto data independent execution latency compliance

Open
#2,202 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Component:RTL Type:Enhancement
Dominant language
SystemVerilog
Stars
2.1k
Forks
810
Avg merge
5d 23h
Merged PRs (30d)
9

Description

The Zkt extension is complied with where a certain subset of instructions have guaranteed data independent latency. Ibex can likely meet this. We should review the requirements in detail and declare compliance.

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 Zkt extension requirements in detail, then assess whether Ibex's relevant scalar cryptographic instructions provide guaranteed data-independent execution latency. Done means documenting the assessment and either declaring compliance or recording the gaps that prevent it.

Written by the indexing model from the issue text.

Assessment

Domain
security
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.