# Certbot 1.3.0 Release

**URL:** <https://community.letsencrypt.org/t/certbot-1-3-0-release/115107>\
**Category:** Client dev\
**Created:** [March 3, 2020, 9:32pm UTC](https://community.letsencrypt.org/t/certbot-1-3-0-release/115107 "2020-03-03T21:32:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![bmw](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmw/32/7797_2.png) [@bmw](https://community.letsencrypt.org/u/bmw)\
**Post date:** [March 3, 2020, 9:32pm UTC](https://community.letsencrypt.org/t/certbot-1-3-0-release/115107/1 "2020-03-03T21:32:25Z")

</div>

Certbot 1.3.0 has just been released. The changelog entry for the release is:

## 1.3.0 - 2020-03-03

### Added

- Added certbot.ocsp Certbot’s API. The certbot.ocsp module can be used to  
determine the OCSP status of certificates.
- Don’t verify the existing certificate in HTTP01Response.simple\_verify, for  
compatibility with the real-world ACME challenge checks.

### Changed

- Certbot will now renew certificates early if they have been revoked according  
to OCSP.
- Fix acme module warnings when response Content-Type includes params (e.g. charset).
- Fixed issue where webroot plugin would incorrectly raise `Read-only file system`  
error when creating challenge directories (issue #7165).

More details about these changes can be found on our GitHub repo.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [March 4, 2020, 1:58am UTC](https://community.letsencrypt.org/t/certbot-1-3-0-release/115107/2 "2020-03-04T01:58:33Z")

</div>

> [@bmw](#):
>
> Certbot will now renew certificates early if they have been revoked according  
> to OCSP.

Potentially useful for the 3/4 revocations...  
But that may depend on how soon OCSP can respond with those revocations.

---

<div class="post-metadata">

**Author:** ![tdelmas](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/tdelmas/32/1866_2.png) [@tdelmas](https://community.letsencrypt.org/u/tdelmas)\
**Post date:** [March 4, 2020, 10:55am UTC](https://community.letsencrypt.org/t/certbot-1-3-0-release/115107/3 "2020-03-04T10:55:10Z")

</div>

> [@rg305](#):
>
> But that may depend on how soon OCSP can respond with those revocations.

The relevant issue with details: [Check OCSP as part of determining if the certificate is due for renewal · Issue #1028 · certbot/certbot · GitHub](https://github.com/certbot/certbot/issues/1028)  
And the relevant PR: [https://github.com/certbot/certbot/pull/7829](https://github.com/certbot/certbot/pull/7829)

---

<div class="post-metadata">

**Author:** ![bmw](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bmw/32/7797_2.png) [@bmw](https://community.letsencrypt.org/u/bmw)\
**Post date:** [April 3, 2020, 10:55am UTC](https://community.letsencrypt.org/t/certbot-1-3-0-release/115107/4 "2020-04-03T10:55:17Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
