2.11.0 was just released! Here's the changelog: Changed In anticipation of backwards incompatible changes, certbot-dns-cloudflare now requires less than version 2.20 of Cloudflare's python library. Fixed Fixed a bug in Certbot where a CSR's SANs did not always follow the order of the domain na…

[image] wgreenberg: Fixed a bug in Certbot where a CSR's SANs did not always follow the order of the domain names that the user requested interactively. In some cases, the resulting cert's common name might seem picked up randomly from the SANs when it should be the first item the user had in…

While Let's Encrypt might do that (I don't know and didn't check :slight_smile: ) there are other ACME CAs that depend on the order. I had a similar bug report for the Ansible acme_certificate module recently; I stored the names in a set (which has a 'random' order) and thus sent them in a different…

Let’s Encrypt promotes the first eligible domain from the CSR to the CN, unless a CN is provided in the CSR. The names are eventually sorted to produce the SANs in the certificate. There was an unintentional change in 2023 that used the sorted list instead but that was quickly reverted. (Eligible…

Certbot 2.11.0 Release

Client dev

Topic		Replies	Views
Subject Alternative Names order not retained Issuance Policy	7	1650	September 15, 2021
Latest renewal changes certificate CN with certbot 1.22.0 Help	3	592	June 3, 2023
Certbot picks up wrong CN from the SAN list while renewing/creating cert Help	10	1511	August 17, 2023
Domain ordering not respected, unexpected certificate subject Help	32	3918	May 26, 2023
Common Name change after using --expand flag Issuance Tech	7	6819	May 26, 2016

Certbot 2.11.0 Release

Related topics