Web server Caddy 2.10 released with ECH, post-quantum key exchange, and more enhancements

Web server Caddy 2.10 released with ECH, post-quantum key exchange, and more enhancements

Caddy, a fast and extensible multi-platform HTTP web server, has launched its latest version, 2.10, introducing several enhancements and bug fixes. A key feature in this release is Encrypted ClientHello (ECH), which encrypts the last plaintext portion of a TLS connection — the ClientHello — to enhance privacy by concealing the domain name being connected to.

Version 2.10 also integrates Post-quantum (PQC) key exchange, with support for the standardized x25519mlkem768 cryptographic group by default. Additionally, Caddy now supports ACME profiles, an experimental draft allowing more flexible certificate properties compared to traditional CSR methods.

The reverse proxy functionality has been updated to set a Via header instead of a duplicate Server header. Users can now specify a default global DNS module, eliminating the need to configure it locally across various parts of the configuration. Moreover, Caddy will now utilize wildcard certificates by default for subdomains, reducing the need for individual certificates for each domain.

Lastly, the libdns APIs have been updated to version 1.0 beta, and a new dns global option allows users to specify DNS provider configuration in a single location, streamlining credential management for servers with domains managed by a single DNS provider.

by Paul

justarandom
justarandom found this interesting
MORE ABOUT: #Web Servers#Caddy
Caddy iconCaddy
  62
  • ...

Caddy is a web server designed with distinct goals and features compared to traditional servers like Apache or nginx. It offers a straightforward installation process and built-in HTTPS support, including integration with Let's Encrypt for automatic certificate management. Caddy is rated 5 and is often compared to alternatives such as nginx, Apache HTTP Server, and Ferron.

Comments

ytrejivis6ewu9x60qdr
1

It should be noted that in order for Caddy to use wildcard certificates for subdomains, you also need to have a wildcard site configured. Otherwise it will still issue individual certificates. From the changelog: "now wildcards, if present, will be utilized for subdomains, rather than obtaining individual certificates."

Gu