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

Remove DNS CERT support. #18

Merged
merged 1 commit into from
Dec 2, 2017
Merged

Remove DNS CERT support. #18

merged 1 commit into from
Dec 2, 2017

Conversation

lambdafu
Copy link
Collaborator

@lambdafu lambdafu commented Dec 2, 2017

DNS CERT is a standard for key retrieval over DNS. This is the authoritative document:

I am removing support for DNS CERTs from NeoPG:

  • There is very low adoption, even less than for PKA and just slightly more than OPENPGPKEY. Of 624 Debian email addresses, only one registered a PGP key, and 3 registered an IPGP URL. The PGP key was registered by the author of the RFC, Simon Josefsson. Two of the IPGP entries did not point to valid PGP data, and one lead to a redirect to PGP data (HTTP 301 Moved Permanently), which GnuPG does not follow. There was also a high rate of errornous or irrelevant responses.
  • RFC 7929 recommends against RFC 4398:

    The OPENPGPKEY RRtype somewhat resembles the generic CERT record
    defined in [RFC4398]. However, the CERT record uses sub-typing with
    many different types of keys and certificates. It is suspected that
    its general application of very different protocols (PKIX versus
    OpenPGP) has been the cause for lack of implementation and
    deployment. Furthermore, the CERT record uses sub-typing, which is
    now considered to be a bad idea for DNS.

  • All arguments against key retrieval via DNS apply (web bugs, lack of security in DNS, lack of control over DNS by users, difficulty of setting up DNS records, etc).

As this is the last DNS record type for key retrieval in the code, I also removed all supporting code in dirmngr.

In the future, NeoPG will provide an API to extend key retrieval and trust evaluation, allowing such protocols to be included in applications without tainting the core code base.

@lambdafu lambdafu merged commit 1881021 into master Dec 2, 2017
@lambdafu lambdafu deleted the no-dns-certs branch December 2, 2017 12:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant