Daniel McCarney

Sorry :robot: but this is still unsupported in the `acme` module. I think it's an important part of RFC 8555. It would help us improve the integration test coverage in...

@bmw To reduce confusion it might be a good idea to edit the issue description to update the documentation links. The up-to-date reference is [RFC 8555 Section 7.3.5](https://tools.ietf.org/html/rfc8555#section-7.3.5). There are...

@c33s The baseline requirements do not permit any publicly trusted CA to issue end entity certificates with an ed25519 public key at this time. Only RSA and ECDSA (with a...

> If the ACME server exposes a "caa-identities" key in its /directory response's "meta" key, Certbot should expose that to users so that they know what string to use if...

One nice feature offered by F-Droid not addressed by Github releases is the ability to [share the app directly between devices](https://f-droid.org/en/tutorials/swap/).

:wave: FWIW Boulder has the same divergence: https://github.com/letsencrypt/boulder/blob/9a86abc1550425a73f912c25a11c29160f58a85a/sa/sa.go#L1218-L1221

Another potential use case (from https://github.com/letsencrypt/pebble/issues/177): checking which certificates have been revoked as a light-weight alternative to OCSP or trying to revoke the certificate again.

@adferrand That sounds great :+1: I like the idea of putting it on a separate port and disabling the administrative interface outright if it isn't configured. Thanks for volunteering to...

I'm going to re-open this issue since while there is a separate HTTP(s) management interface thanks to @adferrand (:tada:) it doesn't yet let you inject test data, query expiration data,...

Seems like a reasonable request :+1: I probably won't have a chance to implement this short term but would accept a PR from the community.