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

DNSSEC failure when using algo 15 #84

Closed
klaver opened this issue Mar 2, 2018 · 10 comments
Closed

DNSSEC failure when using algo 15 #84

klaver opened this issue Mar 2, 2018 · 10 comments
Assignees
Labels
P-High Priority: Issue to be solved before other T-Bug Type: Bug in software or error in test case description
Milestone

Comments

@klaver
Copy link

klaver commented Mar 2, 2018

Tested with domain: ed25519.nl
https://www.zonemaster.net/result/4a6dafd847b4f337

Edit: Updated the link to make up for a change in the URL scheme at zonemaster.net. /@mattias-p

@matsduf
Copy link
Contributor

matsduf commented Mar 2, 2018

This issue should possibly be moved to the Zonemaster-LDNS issues since the verification is done by LDNS code. Could it be that we need a newer version of OpenSSL? It looks like support of Ed25519 came to OpenSSL in version 1.1.0. Is LDNS compatible with that?

@matsduf
Copy link
Contributor

matsduf commented Mar 5, 2018

(@klaver, you sent an email to contact@zonemaster.net. By mistake I erased it. Please send it again.) Forget it, I found it.

@klaver
Copy link
Author

klaver commented Mar 5, 2018

@matsduf the contents of that e-mail where exactly the same as this issue

@matsduf matsduf assigned matsduf and unassigned mattias-p May 29, 2019
@matsduf matsduf assigned mattias-p and unassigned matsduf Jun 19, 2019
@mattias-p mattias-p transferred this issue from zonemaster/zonemaster Jun 19, 2019
@mattias-p
Copy link
Member

The specification says algo 15 should be ALGORITHM_OK which is correct so this isn't a bug in the specification. So I pushed issue down to zonemaster-engine repo.

@andreasschulze
Copy link

andreasschulze commented Aug 7, 2019

poking through my buildlog, I saw "cpanm --notest Zonemaster::LDNS" trigger a download "http://www.cpan.org/authors/id/Z/ZN/ZNMSTR/Zonemaster-LDNS-2.0.1.tar.gz"
and this file contain ldns-1.7.0 sources

so there seem two things todo:

  1. update the archive above to use ldns-1.7.1
  2. install zonemaster on a plattform using openssl-1.1.1

an other option is to use https://github.com/zonemaster/zonemaster-ldns#internal-ldns
and provide ldns-1.7.1 to the system.

How could I specify "--no-internal-ldns" when installing "cpanm --notest Zonemaster::LDNS" ??

"cpanm --notest --no-internal-ldns Zonemaster::LDNS Zonemaster::Engine Zonemaster::CLI"
fail with "Unknown option: no-internal-ldns"

@matsduf
Copy link
Contributor

matsduf commented Aug 8, 2019

When installing with cpanm you cannot use external ldns. You have to follow the installation instructions how to install zonemster-ldns from source.

Thank you for poiting version 1.7.1 of LDNS out. We discovered that there is a new version available when analyzing your issue zonemaster/zonemaster#796 yesterday. We will of course incorporate that in next version of Zonemaster.

@andreasschulze
Copy link

andreasschulze commented Aug 8, 2019

well, it is possible to use external ldns :-)

cpanm --notest --configure-args="--no-internal-ldns" Zonemaster::LDNS

the Announcement for ldns-1.7.1 happened on a mailing list only. I'll ping nlnetlabs to update the website, too ...

@matsduf matsduf transferred this issue from zonemaster/zonemaster-engine Sep 9, 2019
@matsduf matsduf added the T-Bug Type: Bug in software or error in test case description label Sep 9, 2019
@matsduf matsduf added this to the v2019.2 milestone Sep 9, 2019
@matsduf matsduf added the P-High Priority: Issue to be solved before other label Sep 9, 2019
@matsduf
Copy link
Contributor

matsduf commented Sep 9, 2019

This issue covers the same bug as in #51, but with new information on LDNS.

@matsduf
Copy link
Contributor

matsduf commented Oct 10, 2019

PR #85 will resolve this issue.

@matsduf
Copy link
Contributor

matsduf commented Oct 31, 2019

Resolved by #85.

@matsduf matsduf closed this as completed Oct 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-High Priority: Issue to be solved before other T-Bug Type: Bug in software or error in test case description
Projects
None yet
Development

No branches or pull requests

4 participants