theupdateframework / theupdateframework/python-tuf
Add an FAQ and/or high-level overview of how to integrate TUF
还没有人认领这个 Issue。
- 主要语言
- Python
- 星标
- 1.7k
- 派生
- 304
- 平均合并
- 1 天 2 小时
- 30 天内合并 PR
- 17
描述
We are often asked the same questions regarding delegations, how to organize TUF metadata, key management, etc. There should be an FAQ page for these sorts of questions.
The Survivable Key Compromise paper provides an overview of TUF's design, and the specification and other documents available here capture most of what it contains. However, the integration side of things is not adequately explained outside of the Diplomat and Mercury papers. The PEP 458 document is also a good resource for how to integrate TUF with an existing software updater and community repository.
We should provide a condensed, high-level document that contains the information in the papers and documents that have been written since the Survivable Key Compromise paper.
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
调研方向
审阅 Survivable Key Compromise、Diplomat 和 Mercury 论文,以及 PEP 458 文档和现有的 TUF 规范材料。将其中的集成指导整理成一份精简的 FAQ 或高级概览,涵盖委派、元数据组织和密钥管理;当一份易于理解的文档解释了反复出现的集成问题时,即视为完成。
由索引模型根据 Issue 内容生成。
评估
- 领域
- documentation, security
- Issue 类型
- 文档
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100