Discussion: Difficult initialisation error

未关闭
  • 哪里不对？
#793 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
38/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
停滞
技术栈
cpp
领域
security

调研方向

Start at src/lib/SoftHSM.cpp, around line 567, where initialization handles a missing configuration file. Read the surrounding error handling and compare the proposed CKR_FUNCTION_FAILED and CKR_DEVICE_ERROR codes to determine which best fits. Done means the project has an agreed error code and a pull request implementing it; the issue does not identify tests to run.

由索引模型根据 Issue 内容生成。

描述

When SoftHSM is missing its config file it exits with a CKR_GENERAL_ERROR which I think is somewhat misleading as this is generally seen as some hopeless situation where a catastrophic error has occurred and does not hint to something as simple as config missing. I think it would be more useful to a developer if instead at this point we returned a CKR_FUNCTION_FAILED or CKR_DEVICE_ERROR which hint more at invalid configuration/data. I don't know the answer here so was looking for input on what I think is something which could be improved, with an agreed approach I am happy to build the PR implementing it.

https://github.com/softhsm/SoftHSMv2/blob/557b2fd49c64639c4b13416283d91a60748d61a7/src/lib/SoftHSM.cpp#L567

主要语言
C++
星标
1.1k
派生
434
平均合并
12 天 14 小时
30 天内合并 PR
2

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

softhsm/SoftHSMv2 的其他 Issue

查看 softhsm/SoftHSMv2 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。