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

More IP SANs, More IPv6 #900

Closed
wants to merge 17 commits into from
Closed

Conversation

demarcush
Copy link
Contributor

Be sure to take your time as I'm submitting this as a draft first, it's a huge PR.

The goal is to improve the reachablity of servers with using SANs and IPv6, and also correcting mistakes here and then.

Why using IP SANs? Anti-censorship reasons; State actors around the world has started blocking DoH traffic with SNI inspection, removing that single point of failure in the chain results in such actors resort to active probing and/or blocklisting IP ranges, both of which are costly enough to reduce the incentive for them to do as such.

@demarcush
Copy link
Contributor Author

It was so huge it broke the PRCheck. :)

Update hash and add extra IPv4
Update hash yet again; They use different certs for different addresses.
@demarcush
Copy link
Contributor Author

demarcush commented May 13, 2024

These logs are sure giving me a headache. I'm considering closing this.
Should I submit the changes one PR at a time or make another branch and submit the draft first-hand so that prcheck would be able to check every step of the way?
@jedisct1

@jedisct1
Copy link
Member

prcheck found errors: https://github.com/DNSCrypt/dnscrypt-resolvers/actions/runs/9056401552/job/24878890291?pr=900#step:3:916

But yes, splitting this into multiple PRs doing only one class of changes at a time would be much better.

@demarcush
Copy link
Contributor Author

Alright, just didn't want to spam the PR section. But now that you say so.

@demarcush demarcush closed this May 14, 2024
@DNSCrypt DNSCrypt locked and limited conversation to collaborators Jun 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants