-
Notifications
You must be signed in to change notification settings - Fork 15
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 validation of CNAME records is incorrect #33
Comments
Thank you Simson! This is indeed a bug in getdns' native DNSSEC validation code. Note I haven't looked deeply into it yet, but I strongly suspect that the This bug is triggered only when querying directly for CNAME in stub I will write a patch ASAP and consult with my fellow developers how to Thank you very much for finding and reporting this! Much appreciated! -- Willem Toorop Op 07-09-15 om 23:18 schreef Simson L. Garfinkel:
|
Hi Simson, Attached patch resolved the issue and can be applied to version 0.3.0, libtoolize -ci first. Thanks again for finding and reporting this bug! -- Willem Op 07-09-15 om 23:18 schreef Simson L. Garfinkel:
|
Hmmm... I didn't see the attachment in github, so here printed verbatim:
|
Sorry, white spaces are lost that way. You can download the patch here: |
Thanks for the patches. As an aside, I keep getting this error when I compile getdns with the Traceback (most recent call last):
ImportError: /usr/local/lib/libgetdns.so.1: undefined symbol: SRP_Calc_A My only way around this has been to remove openssl-0.1.2d from the path Any idea what might be causing that? On Tue, Sep 8, 2015 at 5:42 AM, wtoorop [email protected] wrote:
|
Sorry for the late response. I haven't been able to reproduce yet. Do you see this with the Not that it should matter, but are your libldns and/or libunbound linked -- Willem Op 08-09-15 om 14:52 schreef Simson L. Garfinkel:
|
You are correct. The getdns and libunbound were linked against different openssls.
|
It seems that DNSSEC lookups of CNAME records that are digitally signed are turning the value BOGUS.
Consider this example program, which performs a RRTYPE_A and then an RRTYPE_CNAME lookup of
www.nist.gov
and prints all of the responses:Here is the execution:
As you can see, it says that the results of the A lookups are secure, but the result of the CNAME lookup is bogus.
However, when I use dig, I am told that the CNAME lookup is properly signed:
The text was updated successfully, but these errors were encountered: