-
Notifications
You must be signed in to change notification settings - Fork 43
Handling malformed/forged _domainconnect RR #180
Copy link
Copy link
Open
Labels
IETFIssues reported from IETF processIssues reported from IETF processIETF Draft: CorePrioIssues with priority to talk aboutIssues with priority to talk about
Description
https://mailarchive.ietf.org/arch/msg/dconn/ZBOHz9sE-y7DbGtaaeTiaLlFFoM
I also realised a more dangerous scenario: malicious domain with _domainconnect record pointing to malformed http resource / oversized file etc. (potential DoS of Service Provider), or internal URL of server infrastructure. I think these are additions to Security Considerations I would take.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
IETFIssues reported from IETF processIssues reported from IETF processIETF Draft: CorePrioIssues with priority to talk aboutIssues with priority to talk about