Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Refactor MechanismWithParam

未关闭
#98 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
停滞
技术栈
python

调研方向

Start by locating MechanismWithParam, mechanism_param, and the current mechanism handling, then read the discussion on pull request 97. Define how Mechanism accepts CK_MECHANISM or a Mechanism instance and how typed subclasses allocate PKCS#11 parameter structures. Done means the old mechanism_param approach is removed and the new extensible API supports the described default and subclass forms.

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

描述

enhancement

MechanismWithParam was a hack to allow for various param mechanisms, but it doesn't scale.

mechanism_param should be removed and mechanism be replaced to allow either a CK_MECHANISM or a Mechanism class.

The default Mechanism class would be mechanism=Mechanism(CK_MECHANISM, param=...) passing mechanism=CK_MECHANISM would be equivalent to mechanism=Mechanism(CK_MECHANISM).

The Mechanism class could be inherited to provide for specific, typed mechanisms Mechanism.RSA_PKCS_PSS(params...) these would be responsible for allocating their appropriate structure in PKCS#11 and passing it as the mechanism parameter.

This is both more Pythonic, typeable (when typing is added to python-pkcs11) and allows for extension into more mechanism types, including extension outside of python-pkcs11.

See the discussion in https://github.com/danni/python-pkcs11/pull/97#discussion_r502974498 for more information.

主要语言
Python
星标
171
派生
79
平均合并
14 小时 23 分钟
30 天内合并 PR
1

环境准备

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

从这里开始

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

pyauth/python-pkcs11 的其他 Issue

查看 pyauth/python-pkcs11 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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