Enable EDNS0 in generated /etc/resolv.conf #2
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
EDNS0 is necessary to make OpenSSH trust DNSSEC-signed SSHFP records found in DNS. Unbound correctly implements EDNS0, so enabling it should be safe. To test, try `ssh -o VerifyHostKeyDNS=yes redpilllinpro01.ring.nlnog.net`.
|
Thanks for the code! Committed part of your fix and also the issue in #5 fix. What I did not add was the check that the edns0 option or trust-ad option must be present. Right now it loops over the file and ignores options that are set. I think this is the most lenient to check what it needs there. |
|
The commit above was not enough, this commit is also needed: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
EDNS0 is necessary to make OpenSSH trust DNSSEC-signed SSHFP records found in DNS. Unbound correctly implements EDNS0, so enabling it should be safe.
To test, try
ssh -o VerifyHostKeyDNS=yes redpilllinpro01.ring.nlnog.net.