# Certbot 1.25.0 Release **URL:** \ **Category:** Client dev\ **Created:** [March 16, 2022, 8:35pm UTC](https://community.letsencrypt.org/t/certbot-1-25-0-release/173954 "2022-03-16T20:35:02Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![erica](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/erica/32/8648_2.png) [@erica](https://community.letsencrypt.org/u/erica)\ **Post date:** [March 16, 2022, 8:35pm UTC](https://community.letsencrypt.org/t/certbot-1-25-0-release/173954/1 "2022-03-16T20:35:03Z")
Certbot 1.25.0 has just been released. The changelog for the release is: ## 1.25.0 - 2022-03-16 ### Changed - Dropped 32 bit support for the Windows beta installer - Windows beta installer is now distributed as "certbot-beta-installer-win\_amd64.exe". Users of the Windows beta should uninstall the old version before running this. - Added a check whether OCSP stapling is supported by the installer when requesting a certificate with the `run` subcommand in combination with the `--must-staple` option. If the installer does not support OCSP and the `--must-staple` option is used, Certbot will raise an error and quit. - Certbot and its acme module now depend on josepy\>=1.13.0 due to better type annotation support. ### Fixed - Updated dependencies to use new version of cryptography that uses OpenSSL 1.1.1n, in response to [https://www.openssl.org/news/secadv/20220315.txt](https://www.openssl.org/news/secadv/20220315.txt). More details about these changes can be found on our GitHub repo. This release is being done mid-month to pickup several security fixes in our dependencies, and is a minor release (rather than a point release) due to a deprecation in our testing pipeline since the last minor release. We do not anticipate any issues caused by the change in timeline, but any unanticipated issues can be mentioned in this thread. ---
**Author:** ![webprofusion](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/webprofusion/32/85310_2.png) [@webprofusion](https://community.letsencrypt.org/u/webprofusion)\ **Post date:** [March 18, 2022, 7:26am UTC](https://community.letsencrypt.org/t/certbot-1-25-0-release/173954/2 "2022-03-18T07:26:50Z")
Very minor nit - I'd say it's the convention on Windows to label 64-bit binaries as x64 (or just to not include the bitness at all, all current versions of windows are 64-bit). amd64 is the old-fashioned name and it's confusing to users if you have an intel CPU (obviously it refers to the instruction set not the manufacturer, but that's not apparent to users). It's still common in some build tools but less so in end-user facing stuff. On a more significant note it would be advisable to prioritize using a signed executable on Windows. The current version can't pass the windows smartscreen check because it's not signed. ---
**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\ **Post date:** [March 18, 2022, 7:56am UTC](https://community.letsencrypt.org/t/certbot-1-25-0-release/173954/3 "2022-03-18T07:56:59Z")
> [@webprofusion](#): > > On a more significant note it would be advisable to prioritize using a signed executable on Windows. The current version can't pass the windows smartscreen check because it's not signed. See [Make the Certbot Windows installer trusted by Windows · Issue #8046 · certbot/certbot · GitHub](https://github.com/certbot/certbot/issues/8046) and also [https://github.com/certbot/certbot/pull/9076](https://github.com/certbot/certbot/pull/9076) for progress on that. ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [April 17, 2022, 7:57am UTC](https://community.letsencrypt.org/t/certbot-1-25-0-release/173954/4 "2022-04-17T07:57:41Z")
Closed on April 17, 2022, 7:57am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.