3 ms·
It was included in the Certbot 1.3.0 release today. https://community.letsencrypt.org/t/certbot-1-3-0-release/115107 https://community.letsencrypt.org/t/certbo
by schoen 7y ago
It was included in the Certbot 1.3.0 release today.
https://community.letsencrypt.org/t/certbot-1-3-0-release/115107 https://community.letsencrypt.org/t/certbot-1-3-0-release/11...
(only certbot-auto users are likely to get this release immediately)
- tialaramex 7y agoDo you have analytics that give you some idea what fraction of subscribers use different versions of Certbot and other ACME clients ? The API is HTTP so presumably all clients could provide an HTTP user agent, although obviously some will show up as generic library defaults. Was this feature something already planned (albeit presumably not for release today) or was it entirely inspired by this problem? I confess if you'd asked me "What extra features does Certbot need?" I would not have listed "Check OCSP to trigger renewal" though in hindsight it's a good idea.
- schoen 7y ago> Do you have analytics that give you some idea what fraction of subscribers use different versions of Certbot and other ACME clients? Those do exist, though I don't personally have access to them. When things are calmer, you might ask bmw or jsha on the Let's Encrypt forum for some more information. > Was this feature something already planned (albeit presumably not for release today) or was it entirely inspired by this problem? I wrote (incomplete) code for this feature several years ago -- specifically inspired by the idea that certificates might sometimes be revoked unexpectedly -- but I don't think anyone planned to continue working on it until this problem came around.