Reference the OpenSSL ECH feature branch rather than the defo-project fork #17251
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.
This PR just changes the recommended OpenSSL git repository to use when building the experimental ECH support. We used to reference the defo-project fork, but (together with OpenSSL maintainers) we have now upstreamed enough ECH code into the OpenSSL project;s ECH feature branch that that can now be used for ECH-enabled curl builds.
The OpenSSL project's feature branch seems more "official" so is probably a better thing to reference for curl documentation. Note though that ECH is not yet part of an OpenSSL release, so it's still not very official, but we are working on that.
The only change here is to the docs/ECH.md build instructions.
I'm not sure if this PR is suited for merging during the feature freeze or not. Either's fine. If there's a preference to not merge this and keep referencing the defo-project fork until ECH is part of an OpenSSL release, that's also fine.