aszlig 1b1f85a156 acme: Don't restrict challenge types (#1522) ... When testing my Stalwart deployment with Pebble[1], I got the following ACME error: ACME error (acme.error) { reason = "unknown variant `dns-account-01`, expected one of `http-01`, `dns-01`, `tls-alpn-01` at line 15 column 33", details = JSON deserialization failed } In RFC 8555 section 8[2], the validation challenges are meant to be extensible: > The identifier validation challenges described in this section all > relate to validation of domain names. If ACME is extended in the > future to support other types of identifiers, there will need to be > new challenge types, and they will need to specify which types of > identifier they apply to. The mentioned error refers to the following draft: https://datatracker.ietf.org/doc/html/draft-ietf-acme-dns-account-label-01 Pebble already implemented[3] this and while it's IMHO too early to already support this in Stalwart, we should at least make sure that we don't break existing deployments in case ACME CAs one day add more challange types like the above. [1]: https://github.com/letsencrypt/pebble [2]: https://datatracker.ietf.org/doc/html/rfc8555#section-8 [3]: https://github.com/letsencrypt/pebble/pull/435 Signed-off-by: aszlig <aszlig@nix.build>		2025-05-25 10:43:59 +02:00
..
src	acme: Don't restrict challenge types (#1522)	2025-05-25 10:43:59 +02:00
Cargo.toml	Bump open-telemetry to 0.29, tokio to 1.45	2025-05-21 15:49:26 +02:00