Tracking issue for constant-time implementation problems
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 20/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- rust
- 领域
- cryptography, security
调研方向
Start by reading the linked draft-irtf-cfrg-rsa-guidance sections and reviewing related issues #710, #702, and #626 to identify which recommendations remain unaddressed. This is a broad tracking issue with existing contributors working on it; done means a specific unchecked recommendation is resolved and its checklist entry can be marked complete, with coordination before any contribution.
由索引模型根据 Issue 内容生成。
描述
draft-irtf-cfrg-rsa-guidance contains plenty of guidance for how to implement RSA in constant time correctly. This is an issue tracking what parts of its recommendations we're currently missing.
Note we have a separate issue #626 specifically to track padding defects and the lack of implicit rejection on padding failures.
- Make private-result integer-to-octet conversion fixed-width and constant-time (see §6.1, §7.2, partly addressed in #710)
- Ignore the first encoded-message octet when depadding OAEP (see §7)
- Apply base blinding by default across private-key operations (see §6.1, partly addressed in #702)
- Audit and replace CRT reductions using division by secret primes including
rem_vartimefor mod reduce (see §6.1, §6.2) - Derive private arithmetic buffer widths from the public modulus (§6.2.1)
- Add fresh exponent blinding for each private operation (see §6.4)
- Add CRT modulus blinding (see §6.5)
- Require exactly
kciphertext octets for PKCS#1 v1.5 decryption (see §7.2, addressed in #710)
NOTE: I'd kindly request that people do NOT open PRs that try to vibe code solutions to these problems. We already have people including myself working on these issues and vibe coded PRs clutter the tracker and just generally waste my time.
- 主要语言
- Rust
- 星标
- 673
- 派生
- 192
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
RustCrypto/RSA 的其他 Issue
-
Silent salt_len truncation in signature_algorithm_identifier() causes signature verification failures可能已有人在做 @cong-or 于 71 天前认领。 未关闭
难度 3/5 半天 新手友好度 74/100
RustCrypto/RSA#703 ·
-
难度 4/5 3-5 天 新手友好度 48/100
RustCrypto/RSA#686 · 4 条评论 ·
-
难度 5/5 一周以上 新手友好度 35/100
RustCrypto/RSA#647 · 10 条评论 · 2 个 reaction ·
-
broken rust docs未关闭
难度 4/5 3-5 天 新手友好度 35/100
RustCrypto/RSA#641 · 3 个 reaction ·
-
难度 5/5 一周以上 新手友好度 25/100
RustCrypto/RSA#640 ·
相似的 Issue
-
agent:triaged bug bughunt pm:npm priority:p1
难度 2/5 1-3 小时 新手友好度 85/100
SocketDev/socket-patch#1127 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
-
documentation enhancement
难度 2/5 1-3 小时 新手友好度 62/100
adorsys/status-list-server#619 ·
维护者通常 2 天内回复
-
batch-backport only backports the first 30 matching PRs可能已有人在做 @DvirDukhan 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 5 天内回复
-
Configuration-level resource: `Allocate` rejects the kubelet's re-offer of the same device for a later container of the same Pod ("Unable to claim slot")可能已有人在做 @fang80913 于 38 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 85/100
project-akri/akri#854 ·