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

Example of Letsencrypt handling

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

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞

调研方向

该 issue 没有指出任何仓库文件或测试。先阅读 Let's Encrypt 的 CAA 参考资料和链接的 TEE-controlled domain certificates 设计,然后明确交付物应是已实现 CAA 方法的示例,还是对 encumbered DNS 的研究;形成有文档记录且达成一致的方法后即视为完成。

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

描述

encumbrance enhancement

There are a few ways of automating domain handling from within an enclave.

  • 1. A starting point is the approach taken in teleport "trust but verify"...

    The private key used to generate the certificate signing request is generated from within the enclave.

The owner of the DNS record isn't proactively prevented from issuing a non-TEE domain, but because certificate transparency provides a list of every issued certificate, we can show a remote attestation to explain every certificate that has been issued.

  • 2. Another improvement is a DNS feature called CAA, https://letsencrypt.org/docs/caa/ which limits the CAs that are authorized to issue certificates for a domain. This significantly reduces the potential for rogue CAs to create MITM attacks - only letsencrypt could do that. This is what is implemented here https://docs.phala.network/dstack/design-documents/tee-controlled-domain-certificates

  • 3. Encumbered DNS: a final step (still to research) would be to encumber the account with the registrar that owns the account. In this way, a smart contract would practically control the DNS records.

主要语言
Python
星标
27
派生
26
平均合并
1 天 6 小时
30 天内合并 PR
12

贡献指南

打开贡献指南

从这里开始

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

Dstack-TEE/dstack-examples 的其他 Issue

查看 Dstack-TEE/dstack-examples 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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