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

respond with servfail if bogus #42

Closed
wants to merge 2 commits into from
Closed

Conversation

buffrr
Copy link
Contributor

@buffrr buffrr commented Sep 12, 2020

When validating DNSSEC, the resolver should return SERVFAIL if DNSSEC validation fails (bogus = true)

example:

dig @1.1.1.1 dnssec-failed.org a

will return SERVFAIL

hnsd only omits the ad flag from the response which makes downgrade attacks possible.

Note: hnsd also considers handshake tlds without a DS RR bogus (they are not secure but they are also not bogus). This should also be fixed because this PR will break handshake tlds that don't use DNSSEC.

Fixed by adding an NSEC record to prove that a DS doesn't exist which allows unbound to treat it as unsigned instead of bogus.

buffrr added 2 commits March 6, 2021 16:10
Adds an NSEC record to indicate that we only have NS NSEC RRSIG. This proves that we don't have a DS rr and allows unbound to treat the zone as unsigned.
@buffrr buffrr changed the title rs: respond with servfail if bogus respond with servfail if bogus Mar 7, 2021
@buffrr buffrr marked this pull request as draft March 9, 2021 20:19
@pinheadmz pinheadmz self-requested a review March 9, 2021 23:19
@pinheadmz pinheadmz mentioned this pull request Nov 20, 2021
8 tasks
@pinheadmz
Copy link
Member

Closed by #76 lets move discussion / review there.

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.

2 participants