Build DNS-published cryptographic identity system#1
Merged
Conversation
Add complete implementation of the Explicit Trust Plane: - Design document (docs/DESIGN.adoc) with architecture rationale - Deployment guide (docs/DEPLOYMENT.adoc) for end-to-end setup - Key generation scripts for Ed448/Ed25519/X25519 and OpenPGP - DNS zone template with CERT, IPSECKEY, TLSA, and CAA records - Justfile recipes for key generation and rotation - README with project overview and quick start guide This framework enables DNS-native cryptographic identity using modern algorithms (Ed448, Ed25519, X25519) with explicit role separation between signing and key exchange.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add complete implementation of the Explicit Trust Plane:
This framework enables DNS-native cryptographic identity using modern algorithms (Ed448, Ed25519, X25519) with explicit role separation between signing and key exchange.