certbot formerly letsencrypt client for Lets Encrypt Certificates
ATTENTION: Version 1.23.0 is the last version which can be use in Leap.
Version >= 1.24 need python3 >= 3.7
Certbot (previously, the Let's Encrypt client) is an easy-to-use automatic client that fetches and deploys
SSL/TLS certificates for your webserver.
Certbot was developed by EFF and others as a client for Let’s Encrypt and was previously known as
“the official Let’s Encrypt client” or “the Let’s Encrypt Python client.”
Certbot will also work with any other CAs that support the ACME protocol.
While there are many other clients that implement the ACME protocol to fetch certificates, Certbot is the
most extensive client and can automatically configure your webserver to start serving over HTTPS immediately.
For Apache, it can also optionally automate security tasks such as tuning ciphersuites and enabling important
security features such as HTTP → HTTPS redirects, OCSP stapling, HSTS, and upgrade-insecure-requests.
Certbot is part of EFF’s larger effort to encrypt the entire Internet. Websites need to use HTTPS to secure
the web. Along with HTTPS Everywhere, Certbot aims to build a network that is more structurally private,
safe, and protected against censorship.
-
1
derived packages
- Download package
-
Checkout Package
osc -A https://api.opensuse.org checkout home:ecsos:server/certbot && cd $_ - Create Badge
Source Files
| Filename | Size | Changed |
|---|---|---|
| README.SUSE | 0000001749 1.71 KB | |
| _link | 0000000130 130 Bytes | |
| certbot-cli.ini.patch | 0000001527 1.49 KB | |
| certbot-fix_constants.patch | 0000001105 1.08 KB | |
| certbot.changes | 0000020438 20 KB | |
| certbot.cron | 0000000949 949 Bytes | |
| certbot.rpmlintrc | 0000000153 153 Bytes | |
| certbot.spec | 0000015705 15.3 KB | |
| v0.25.1.tar.gz | 0001160526 1.11 MB |
Revision 118 (latest revision is 238)
Eric Schirra (ecsos)
committed
(revision 118)
- update to 0.25.1
* Fixed
- TLS-ALPN-01 support has been removed from our acme library.
Using our current dependencies, we are unable to provide
a correct implementation of this challenge so we decided
to remove it from the library until we can provide proper
support.
- Issues causing test failures when running the tests in the
acme package with pytest<3.0 has been resolved.
- certbot-nginx now correctly depends on acme>=0.25.0.
Despite us having broken lockstep, we are continuing to release
new versions of all Certbot components during releases for the
time being, however, the only packages with changes other than
their version number were:
- acme
- certbot-nginx
More details about these changes can be found on our GitHub repo:
https://github.com/certbot/certbot/milestone/56?closed=1
- update to 0.25.0
* Added
- Support for the ready status type was added to acme. Without
this change, Certbot and acme users will begin encountering
errors when using Let's Encrypt's ACMEv2 API starting on
June 19th for the staging environment and July 5th for
production.
See https://community.letsencrypt.org/t/acmev2-order-ready-status/62866
for more information.
- Certbot now accepts the flag --reuse-key which will cause the
same key to be used in the certificate when the lineage is
Comments 2
Does it make sense to use systemd instead of cron? It will be easier to enable/disable in YaST and monitor errors.
I am not a friend of systemd. And certainly not from systemd cron. Sorry.