v2.57.0 (a CA account's EAB key stays out of certbot's log, DNS accounts are no longer overwritten or deleted from under their certificates, and the dashboard says when it could not load)
A minor release. The API contract moves to 2.66: two DNS account requests have a new 409 answer and the backup list is newest first (#1491). Most of it comes from two audits of v2.56.1, one of the interface and one of the operator's flows. Every fix has a test that was run before the change and failed.
-
Security: a CA account's EAB key no longer reaches certbot's log (#1485, closes #1461). certbot writes its whole command line to
<cert>/logs/letsencrypt.logat the start of every run, failed runs included, and CertMate passed the EAB pair of a CA account (ZeroSSL, Google, SSL.com, Actalis, Sectigo, a private CA that binds accounts) on that command line. The key sat in plain text in that log and in every rotated copy. The pair now reaches certbot in a 0600 config file that is removed when the run ends. Measured with certbot 5.8.0: one line with the key in the log before, none after.What changes for you: at the first start of this version, CertMate masks the EAB values in the certbot logs earlier versions left, once, and logs a warning with how many it masked. If it masked any, consider rotating the EAB keys of those CA accounts with the CA. Backups never carried these logs.
-
Fix: creating a DNS account under a name in use no longer replaces it (#1486). The settings page makes the account id from its name, and a second "Production" replaced the first one's credentials and said "created successfully". A create whose name is an account with credentials now answers
409 DNS_ACCOUNT_EXISTSand the account keeps them; change credentials with Edit. The emptydefaultaccount a new instance carries can still be filled in. -
Fix: a DNS account that certificates renew through is not deleted (#1487). The delete answered 200 and the next renewal of those certificates failed. It now answers
409 DNS_ACCOUNT_IN_USEand names the certificates. A certificate with no account recorded renews through the provider's default, so it holds the default. CA accounts already worked this way. -
Fix: when the session ends, the dashboard goes to the login page (#1490). Sessions are kept in memory, so after a restart every open tab's next refresh replaced the list with "Welcome to CertMate" and zero counters. A 401 now goes to the login page and back. A failed refresh keeps the list on screen and says it is the last successful load, and a failed first load says the list could not be loaded, with a retry.
-
Fix: the dashboard asks for one certificate listing at a time (#1483, part of #1463). On an estate of about 2,000 certificates a listing takes seconds, and the dashboard asked for a new one after every action and live event without waiting for the last, so one browser could hold every server thread and
/healthstopped answering. A call made during a listing now shares one queued behind it. Overlapping listings on the server are still slow, and that part of #1463 is open. -
Fix: a failed issuance's hint follows the challenge (#1480, closes #1460). The CA refusing an http-01 answer told the operator to check DNS credentials. The hint now reads the challenge from the CA's words, the request or the instance default, and an http-01 failure points at port 80 and the webroot.
-
Fix: the renewal sweep counts the certificates that are not due yet (#1481, closes #1459). The nightly line read "17 checked, 16 renewed, 0 not-due" on a night when the 17th was rightly left alone. It now says "N not due yet" and, apart, "N declined by certbot".
-
The first admin can be given an email at setup (#1482, part of #1466). An optional field on the setup page, so an operator turning on single sign-on can have the first admin matched by email without editing it afterwards.
-
Backups: the one just made is listed first (#1488). After an hour of automatic backups, the one the operator had just made was behind "Show 8 more".
-
Interface (#1489):
- dialog close buttons were 2.5:1 in light mode and 10 px wide; they are now readable in both themes and 32 px square, and the readability test opens every dialog to check them;
- the new-certificate form is one column, so the Domain and SANs examples are no longer cut from 1024 px up;
- on a 390 px phone the settings badges and the challenge cards no longer break across lines;
- long domains have a tooltip on the dashboard; the client certificate table keeps its chips and dates on one line; Activity shows imports as "Imported".
Known: the certbot command line cannot get a certificate from CertMate's own ACME server, because the chain is the leaf alone (#1484). lego, acme.sh and cert-manager are not affected.