This issue concerns the ECDSA certificate generation feature provided by #8254. It is about to provide proper guidance to users in how to migrate to ECDSA certificates, as described in the design document: https://docs.google.com/document/d/18pr4F4SVim-bSR6izNV5ZYwolnvitTvmP6gqElDdZPU/edit?usp=sharing
Indeed we should write documentation with the recommended workflow for changing an existing certificate and an existing installation to use ECDSA keys, and also for requesting a new ECDSA certificate. This should include a warning that users who obtain certificates with ECDSA keys should be careful to not downgrade their Certbot version if they change installation methods because using ECDSA keys with older versions of the client is not supported by the Certbot team.
When this feature is released, someone from the core Certbot team should post this documentation to the community forum.
This issue concerns the ECDSA certificate generation feature provided by #8254. It is about to provide proper guidance to users in how to migrate to ECDSA certificates, as described in the design document: https://docs.google.com/document/d/18pr4F4SVim-bSR6izNV5ZYwolnvitTvmP6gqElDdZPU/edit?usp=sharing
Indeed we should write documentation with the recommended workflow for changing an existing certificate and an existing installation to use ECDSA keys, and also for requesting a new ECDSA certificate. This should include a warning that users who obtain certificates with ECDSA keys should be careful to not downgrade their Certbot version if they change installation methods because using ECDSA keys with older versions of the client is not supported by the Certbot team.
When this feature is released, someone from the core Certbot team should post this documentation to the community forum.