Re-add adfree.usableprivacy.net (certificate issue) #956
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
markushuber
changed the title
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.
Suggestion cannot be applied right now. Please check back later.
Commit 0899a2a removed our public resolver.
Interesting enough, our monitoring did not detect any service disruptions.
Your build pipelines indicated a certificate hash issue (initially with with this PR). This PR updates our servers stamps based on the
Let's Encrypt R10hash from https://github.com/DNSCrypt/doh-server?tab=readme-ov-file#common-certificate-hashesOverall: It would imho make more sense if one could pin a certain Root CA (e.g. Let's Encrypt) in the dnsstamp instead of intermediate CAs.
P.S.: Any chance that a contact can be provided to enable notification for cases whenever a specific resolver is removed?