Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Example of Letsencrypt handling

未關閉
#6 2 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
25/100
Issue 類型
功能
描述清晰度
需要釐清
活躍度
停滯

研究方向

此 issue 未指出任何 repository 檔案或測試。先閱讀 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
平均合併
4 小時 4 分鐘
30 天內合併 PR
7

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 沒有 Pull Request 範本
  • 閱讀貢獻指南

從這裡開始

  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 摘要。