Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to reference existing type 61 OPENPGPKEY DNS resource records #28

Closed
m-ueberall opened this issue Oct 6, 2017 · 5 comments
Closed

Comments

@m-ueberall
Copy link

The Encryption: directive should allow to reference existing type 61 (OPENPGPKEY) DNS resource records as well (in conjunction with proper DNSSEC signatures, this should be considered more secure).
Independently of the above (e.g., in cases where both a type 61 resource record as well as a link to a file containing a public key exist and both are associated with the same email address), it would be helpful if the standard explicitly suggested what to do in cases where there are inconsistencies.

@nightwatchcyber
Copy link
Contributor

Perhaps we can expand this to reference all kinds of PKI DNS records? I am thinking of the ones defined by DANE:
https://en.wikipedia.org/wiki/DNS-based_Authentication_of_Named_Entities

@nightwatchcyber
Copy link
Contributor

Wondering if we can use the URI scheme for DNS, as per RFC 4501:
https://tools.ietf.org/html/rfc4501

@austinheap
Copy link
Collaborator

FWIW I'm supportive of this given that we use RFC 4501 like @nightwatchcyber suggested.

@nightwatchcyber
Copy link
Contributor

@m-ueberall - would this work?

Encryption: dns:5d2d3ceb7abe552344276d47d36._openpgpkey.example.org?type=OPENPGPKEY

@nightwatchcyber
Copy link
Contributor

This is done for the Encryption field - it allows DNS records to be referenced

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants