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

Fix bogus vs insecure check #28

Open
buffrr opened this issue Mar 19, 2021 · 0 comments
Open

Fix bogus vs insecure check #28

buffrr opened this issue Mar 19, 2021 · 0 comments

Comments

@buffrr
Copy link
Contributor

buffrr commented Mar 19, 2021

I mentioned this in hsd and hnsd as well. Unbound has two variables in the result secure and bogus.

  1. In all cases, if the answer is bogus we should return servfail.
  2. If the answer is secure add the Authenticated Data (AD) bit.
  3. If the answer is not secure set the Authenticated Data (AD) bit to false.

bogus indicates a security failure which means that the result shouldn't be trusted. This allows us to do authenticated denial of existence.

One thing that's nice to have but not necessary is that if the CD bit is set (checking disabled) in the question we probably shouldn't do anything about this and return the bogus result (but it's not really a big deal since they will get servfail from the validating resolver anyway).

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

No branches or pull requests

1 participant