Ability to access certificate extensions through `Crypto` API `X509Certificate` class
还没有人认领这个 Issue。
- 主要语言
- JavaScript
- 星标
- 122k
- 派生
- 37.3k
- 平均合并
- 4 天 2 小时
- 30 天内合并 PR
- 283
描述
What is the problem this feature will solve?
Key usages (not extend) are completely different and can only be accessed through certificate extension under OID 2.5.29.15 which contains value in a bit array format.
Key usage can have for definition: Digital signature, Non-repudiation, Key encipherment, Data encipherment, Key agreement, Certificate signing, CRL signing, Encipher only, Decipher only.
As of now Crypto API only provides access to Extended Key usage under the x509.keyUsage but does not provide access to the Key Usage through the certificate Extensions part.
What is the feature you are proposing to solve the problem?
Having a method the class x509 that can allow to have access to the Extension part of a certificate through a safe structure.
What alternatives have you considered?
Using 3rd party libraries like PKIjs or Forge, but I would like a native feature instead.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
从 Node.js Crypto API 的 X509Certificate 实现以及现有的 x509.keyUsage 行为开始。检查证书扩展和 OID 2.5.29.15 的表示方式,然后定义一种安全的结构来公开 key usage,并验证新的 API 能将其与 extended key usage 区分开来。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- javascript, node.js
- 领域
- backend-api-design, security
- Issue 类型
- 功能
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 25/100