[dns-aid] Initial integration - #15926
Draft
IngmarVG-IB wants to merge 1 commit into
Draft
Conversation
DNS-AID is the reference implementation of IETF draft-mozleywilliams-dnsop-dnsaid (DNS-based AI agent discovery). The harness fuzzes the parsers that consume untrusted DNS record data and HTTP discovery documents.
|
IngmarVG-IB is integrating a new project: |
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.
Project
DNS-AID (https://github.com/dns-aid/dns-aid-core) is the reference implementation of IETF draft-mozleywilliams-dnsop-dnsaid — DNS-based discovery and identification of AI agents. It is published on PyPI as
dns-aidand is on a standards track within the IETF dnsop working group, with the project headed toward Linux Foundation hosting.Why fuzzing matters here
The library's core job is parsing untrusted, attacker-controllable input: DNS SVCB/TXT record data (including RFC 9460 private-use SvcParamKeys), agent FQDNs, DNS-hosted index documents, and JSON discovery documents fetched over HTTP. Any deployment resolves records published by arbitrary third-party domains, so parser robustness is directly security-relevant.
Integration
tests/fuzz/fuzz_parsers.pyand dispatches across the SVCB parameter parser, FQDN parsers, TXT index/value parsers, HTTP index document parser, and input validators. It already runs weekly in the project's own CI.Status
Draft until dns-aid/dns-aid-core#218 (which adds the harness to
main) merges — will mark ready for review right after. Happy to adjust anything about the integration.