fix(deps): update module github.com/caddyserver/caddy/v2 to v2.10.0 #22
No reviewers
Labels
No labels
action
automerge
dependencies
docker
pin-digest
skip-ci
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
homelab/bin-caddy!22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "renovate/github.com-caddyserver-caddy-v2-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
v2.9.1->v2.10.0Release Notes
caddyserver/caddy (github.com/caddyserver/caddy/v2)
v2.10.0Compare Source
Caddy 2.10 is here! Aside from bug fixes, this release features:
x25519mlkem768cryptographic group by default.dnsglobal option in the Caddyfile, or in JSON config, it's thednsparameter in thetlsapp configuration.tls force_automatein the Caddyfile. The experimentalauto_https prefer_wildcardoption has been removed.dnsconfig: Now that several components of Caddy configuration may affect DNS records (ACME challenges, ECH publication, etc.), there is a newdnsglobal option that can be used to specify your DNS provider config in a single place. This prevents repetition of credentials for servers where all the domains are managed by a single DNS provider.Thank you to the many contributors who have helped to make this possible! 🎉 🥳 🍾
⚠️ While have traditionally supported the last 2 minor Go versions to accommodate some distribution / package manager policies, we now only support the latest minor Go version. The privacy and security benefits added in new Go versions (such as post-quantum cryptography) are worth making available to everyone as soon as possible, rather than holding back the entire user base or maintaining multiple code compilation configurations.
Encrypted ClientHello (ECH) details
(This is a brief overview. We recommend reading the full documentation.)
Typically, server names (domain names, or "SNI") are sent in the plaintext ClientHello when establishing TLS connections. With ECH, the true server name is encrypted (and wrapped) by an "outer" ClientHello which has a generic SNI of your choosing. With many sites on the same server sharing the same outer SNI, both clients and the server have more privacy related to domain names.
Caddy implements fully automated ECH, meaning that it generates (and soon, rotates), publishes, and serves ECH configurations simply by specifying a DNS provider, and the outer/public domain name to use.
Fully automated ECH requires a DNS module built into your Caddy binary. In order for a client, such as a browser, to know it can use ECH, and what parameters to use, the server's ECH configuration must be published. This config includes the public name, cryptographic parameters, and a public key for encrypting the inner ClientHello. By convention, browsers read the standardized HTTPS-type DNS record containing a
echSvcParamKey. Caddy sets this DNS record for all domains being protected, but it needs that DNS provider module plugged in and configured in order to do this. If you are already using the DNS ACME challenge, you should already have a DNS provider plugged in. If you prefer to build Caddy from source with a DNS module, it's easy with xcaddy, for example:$ xcaddy build --with github.com/caddy-dns/cloudflareThe minimum config needed to enable ClientHello is also the recommended config, as it maximizes privacy benefits in most situations. You just need the
echglobal option and a DNS provider specified. Here's an example using Cloudflare as the nameserver:Caddyfile:
This protects all your sites (
example.comin this case) behind the public name ofech.example.net. (As another example, Cloudflare usescloudflare-ech.comfor all the sites it serves. We recommend choosing a single public domain and use it to protect all your sites.)The outer/public name you choose should point to your server. Caddy will obtain a certificate for this name in order to facilitate safe, reliable connections for clients when needed. Without a certificate, clients may be forced to connect insecurely, or fail to connect at all, in some cases, which not only leaves them vulnerable, but also risks exposing the names of your server's sites.
Caddy then uses the specified DNS provider to publish the ECH config(s) for your various site names. It creates (or augments) HTTPS-type records for the domains of your sites (not your ECH public name). Note that DNS provider modules are independently-maintained, and may not have been tested for compatibility with HTTPS-type records. Please contact your module's maintainers if you experience issues.
If you have more advanced configuration needs, you can use the JSON configuration (more details coming soon; for now, see #6862 or look at the source code; or use
caddy adaptto convert a Caddyfile to JSON).Testing and verifying Encrypted ClientHello
First make sure Caddy runs successfully with ECH enabled (and a DNS module) in the config. You should see logs that it is generating an ECH config and publishing it to your domain name(s).
You will need to use a client that supports ECH. Some custom builds of
curldo, and Firefox and modern Chrome-based browsers do as well, but you need to enable DNS-over-HTTPS or DNS-over-TLS first (since, obviously, querying DNS in plaintext for a protected domain name will expose the domain and defeat the purpose of ECH).If reusing an existing domain name, clear your DNS cache. Firefox has a way of doing this for its cache at
about:networking#dns.Once you have a suitable client, use Wireshark to capture network packets as you load your site. You should see only the outer/public name as SNI (ServerName Indicator) values in the packet capture. If at any time you see the true site name, ECH is not working properly -- it could be a client or server issue. Before filing a bug, please try to pinpoint it as a server issue first. But definitely report server bugs! Thank you!
(Note that ECH is not automatically published for CNAME'd domains, and the domain must already have a record in the zone.)
Commits
Beta 1:
96c5c55admin: fix index validation for PUT requests (#6824)3644ee3build(deps): bump github.com/cloudflare/circl from 1.3.3 to 1.3.7 (#6876)eacd772build(deps): bump github.com/go-jose/go-jose/v3 from 3.0.3 to 3.0.4 (#6871)9996d6abuild(deps): bump github.com/golang/glog from 1.2.2 to 1.2.4 (#6814)1115158caddyhttp: ResponseRecorder sets stream regardless of 1xx8861eaecaddytest: Support configuration defaults override (#6850)d7764dfcaddytls: Encrypted ClientHello (ECH) (#6862)a807fe0caddytls: Enhance ECH documentationbc3d497caddytls: Fix broken refactor7b8f350caddytls: Fix sni_regexp matcher to obtain layer4 contexts (#6804)2c4295ecaddytls: Initial support for ACME profilesd7872c3caddytls: Refactor sni matcher (#6812)172136acaddytls: Support post-quantum key exchange mechanism X25519MLKEM768066d770cmd: automatically set GOMEMLIMIT (#6809)1f35a8afastcgi: improve parsePHPFastCGI docs (#6779)22563a7file_server: use the UTC timezone for modified time (#6830)cfc3af6fix: update broken link to Ardan Labs (#6800)99073eago.mod: Upgrade CertMagic to v0.21.71641e76go.mod: Upgrade dependencies0d7c639go.mod: remove glog dependency (#6838)932dac1logging: Always set fields func; fix #68299e0e5a4logging: Fix crash if logging error is not HandlerError (#6777)904a0fareverse_proxy: re-add healthy upstreams metric (#6806)e7da3b2reverseproxy: Via header (#6275)9283770reverseproxy: ignore duplicate collector registration error (#6820)Beta 2:
f4432a3caddyfile: add error handling for unrecognized subdirective/options in various modules (#6884)84364ffcaddypki: Remove lifetime check at Caddyfile parse (fix #6878)adbe7f8caddytls: Only make DNS solver if not already set (fix #6880)d57ab21caddytls: Pointer receiver (fix #6885)4ebcfedcaddytls: Reorder provisioning steps (fix #6877)a686f7ccmd: Only set memory/CPU limits on run (fix #6879)1987620cmd: Promote undo maxProcs func to caller220cd1creverseproxy: more comments about buffering and add new tests (#6778)Beta 3:
b3e692ecaddyfile: Fix formatting for backquote wrapped braces (#6903)55c89cccaddytls: Convert AP subjects to punycode1f8dab5caddytls: Don't publish ECH configs if other records don't exist782a3c7caddytls: Don't publish HTTPS record for CNAME'd domain (fix #6922)49f9af9caddytls: Fix TrustedCACerts backwards compatibility (#6889)e276994caddytls: Initialize permission module earlier (fix #6901)39262f8caddytls: Minor fixes for ECH1735730core: add modularnetwork_proxysupport (#6399)86c620fgo.mod: Minor dependency upgradesaf2d33aheaders: Allow nil HeaderOps (fix #6893)dccf3d8requestbody: Add set option to replace request body (#5795)2ac09fdrequestbody: Fix ContentLength calculation after body replacement (#6896)v2.10.0:
f297bc0admin: Remove host checking for UDS (close #6832)0b2802fbuild(deps): bump golang.org/x/net from 0.37.0 to 0.38.0 (#6960)5be77d0caddyauth: Set authentication provider error in placeholder (#6932)b06a949caddyhttp: Document side effect of HTTP/3 early data (close #6936)35c8c2dcaddytls: Add remote_ip to HTTP cert manager (close #6952)fb22a26caddytls: Allow missing ECH meta file1bfa111caddytls: Prefer managed wildcard certs over individual subdomain certs (#6959)ea77a9acaddytls: Temporarily treat "" and "@" as equivalent for DNS publication5a6b2f8events: Refactor; move Event into core, so core can emit events (#6930)137711ago.mod: Upgrade acmez and certmagic9becf61go.mod: Upgrade to libdns 1.0 beta APIs (requires upgraded DNS providers)6c38ae7reverseproxy: Add valid Upstream to DialInfo in active health checks (#6949)What's Changed
archives.format_overrides.formatby @mohammed90 in https://github.com/caddyserver/caddy/pull/6807replacefor optional body replacement by @AdrienPensart in https://github.com/caddyserver/caddy/pull/5795network_proxysupport by @mohammed90 in https://github.com/caddyserver/caddy/pull/6399New Contributors
Full Changelog: https://github.com/caddyserver/caddy/compare/v2.9.1...v2.10.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
ℹ Artifact update notice
File name: go.mod
In order to perform the update(s) described in the table above, Renovate ran the
go getcommand, which resulted in the following additional change(s):godirective was updated for compatibility reasonsDetails:
go1.23.4->1.24github.com/alecthomas/chroma/v2v2.14.0->v2.15.0github.com/caddyserver/certmagicv0.21.6->v0.23.0github.com/cpuguy83/go-md2man/v2v2.0.4->v2.0.6github.com/dgraph-io/ristrettov0.1.1->v0.2.0github.com/dlclark/regexp2v1.11.0->v1.11.4github.com/go-chi/chi/v5v5.0.12->v5.2.1github.com/go-jose/go-jose/v3v3.0.3->v3.0.4github.com/google/cel-gov0.21.0->v0.24.1github.com/klauspost/compressv1.17.11->v1.18.0github.com/klauspost/cpuid/v2v2.2.9->v2.2.10github.com/libdns/libdnsv0.2.2->v1.0.0-beta.1github.com/mholt/acmez/v3v3.0.0->v3.1.2github.com/miekg/dnsv1.1.62->v1.1.63github.com/quic-go/quic-gov0.48.2->v0.50.1github.com/spf13/cobrav1.8.1->v1.9.1github.com/spf13/pflagv1.0.5->v1.0.6golang.org/x/cryptov0.32.0->v0.36.0golang.org/x/crypto/x509roots/fallbackv0.0.0-20241211175049-b4f1988a35de->v0.0.0-20250305170421-49bf5b80c810golang.org/x/modv0.22.0->v0.24.0golang.org/x/netv0.34.0->v0.38.0golang.org/x/syncv0.10.0->v0.12.0golang.org/x/sysv0.29.0->v0.31.0golang.org/x/termv0.28.0->v0.30.0golang.org/x/textv0.21.0->v0.23.0golang.org/x/timev0.8.0->v0.11.0golang.org/x/toolsv0.28.0->v0.31.0## License & Vulnerability Scan
## Build Log
Commit:
fb728fe9f6Actions:
#49