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

NSEC validation failing in nightly #152

Closed
bluejekyll opened this Issue Jun 24, 2017 · 3 comments

Comments

Projects
None yet
1 participant
@bluejekyll
Copy link
Owner

bluejekyll commented Jun 24, 2017

There is something incorrect in the trust-dns-server authority. NSEC validation of publicly signed records functions properly.

cargo test test_nsec_query_example_nonet

which relies on the trust-dns-server Authority fails, while

cargo test test_nsec_query_example -- --ignored

which tests public records, passes


Regression on nightly

Ok, had a minute to track down the nightly version that broke this.

repro with:

rustup run nightly-2017-06-20 cargo test test_nsec_query_example_nonet

Current understanding of issue

  • This appears to be something in the Authority signing logic
  • It only affects NSEC records for some reason, and not signatures of other record types
  • It does not appear to be related to OpenSSL or Ring as both show the same issue, so it may not be signing issue
    • I need to create more tests to validate the signing of the NSEC record type and work up from there to disqualify that
@bluejekyll

This comment has been minimized.

Copy link
Owner Author

bluejekyll commented Jun 25, 2017

Possible root cause: rust-lang/rust#39409

@bluejekyll

This comment has been minimized.

Copy link
Owner Author

bluejekyll commented Jun 28, 2017

the related bug was closed. just need valid test run before closing this: rust-lang/rust#42903

@bluejekyll

This comment has been minimized.

Copy link
Owner Author

bluejekyll commented Jun 29, 2017

🎉 fixed!

@bluejekyll bluejekyll closed this Jun 29, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.