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

Moving attestation generation and verification code to `attest` repo.

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
重构
描述清晰度
需要澄清
活跃度
冷清
技术栈
rust

调研方向

首先阅读 attested-tls 中的 attestation crate 和 pccs crate,然后检查尚未合并的 mock-tdx crate 以及链接的 attest repository。明确 crates 是否应移动到 attest,或者是否应将所有内容都移动到 attested-tls,包括生成和验证的组织方式。当仓库布局和所有权决策达成一致,并且相关 crates 已一致地完成移动时,即视为完成。

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

描述

@alexhulbert has started https://github.com/flashbots/attest which can compute measurements from an OS image together with CVM configuration.

The idea is that CVM configuration data would be sent as part of the attestation evidence payload, and a verifier would use it to compute the expected measurements for that particular instance. Eg: for GCP we would probably include the machine type and region. This would save us needing to have pre-computed measurement values for every combination of accepted OS image version and CVM configuration.

Since this involves both generation and verification, the proposal is to move the contents of the attestation crate over to that repo.

If doing that, it would probably also make sense to move the pccs crate and not-yet-merged mock-tdx crate there as well, as i think they belong together with attestation rather than attested-tls.

The alternative would be to do it the other way around and move everything into this repo.

Tagging @0x416e746f6e as you were not around when we were talking about this last week.

主要语言
Rust
星标
6
派生
3
平均合并
1 天 2 小时
30 天内合并 PR
3

环境准备

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

从这里开始

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

flashbots/attested-tls 的其他 Issue

查看 flashbots/attested-tls 的全部 Issue

相似的 Issue

更多 Rust Issue

把新 issue 发到你的邮箱

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