AES-GCM tests failing with wycherproof in Fedora
评估
调研方向
Start by reproducing the failure with the wycheproof integration test on Fedora and SoftHSM 2.6.9 or 2.7.0; the report identifies test 311 as the likely trigger after test 310. Trace the failing AES-GCM invalid-input case through the SoftHSM code that handles its buffers and compare behavior with the passing Ubuntu CI run. Done means the assertion is resolved and the Wycheproof tests pass.
由索引模型根据 Issue 内容生成。
描述
After trying to update rust-cryptoki in Fedora that got softhsm 2.7.0 I started getting some C++ assertions. They fail in one of the wycherproof test rust-cryptoki introduced in recent release:
test aes_gcm_message_wycheproof ... ok
...
✓ Test 310: Valid - Key: 256-bit, Nonce: 10, Tag: 16, AAD: 0, PT: 16
/usr/include/c++/16/bits/stl_vector.h:1253: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = unsigned char; _Alloc = SecureAllocator<unsigned char>; reference = unsigned char&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
error: test failed, to rerun pass `--test wycheproof`
The same is happening in Fedora 43 with softhsm 2.6.9 (but looks like it does not in upstream CI with Ubuntu):
✓ Test 310: Valid - Key: 256-bit, Nonce: 10, Tag: 16, AAD: 0, PT: 16
/usr/include/c++/15/bits/stl_vector.h:1263: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = unsigned char; _Alloc = SecureAllocator<unsigned char>; reference = unsigned char&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.
I assume the failing input is the next test we are not getting output for (output from testsuite running against kryoptic):
✓ Test 311: Invalid (expected failure) - Key: 128-bit, Nonce: 0, Tag: 16, AAD: 0, PT: 0
I did not dive deeper into the softhsm code, but it sounds like some buffer overrun that should not be there ...
- 主要语言
- C++
- 星标
- 1.1k
- 派生
- 434
- 平均合并
- 12 天 14 小时
- 30 天内合并 PR
- 2
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
softhsm/SoftHSMv2 的其他 Issue
-
C_DigestKey digests a sensitive EC private key's CKA_VALUE: no check that the object is a secret key未关闭
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 78/100
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 4/5 3-5 天 新手友好度 54/100
-
难度 4/5 3-5 天 新手友好度 56/100
查看 softhsm/SoftHSMv2 的全部 Issue
相似的 Issue
-
area/ysql kind/bug priority/medium status/awaiting-triage
难度 2/5 1-3 小时 新手友好度 78/100
yugabyte/yugabyte-db#37523 ·
维护者通常 1 天内回复
-
mlir
难度 2/5 1-3 小时 新手友好度 72/100
llvm/llvm-project#241070 · 1 条评论 ·
维护者通常 1 天内回复
-
backlog documentation
难度 1/5 1 小时以内 新手友好度 96/100
EchoTools/nevr-runtime#2354 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
help wanted new command
难度 2/5 1-3 小时 新手友好度 76/100
tldr-pages/tldr#25111 ·
维护者通常 1 天内回复