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 | 0000012663 12.4 KB | |
| certbot.cron | 0000000949 949 Bytes | |
| certbot.rpmlintrc | 0000000153 153 Bytes | |
| certbot.spec | 0000015566 15.2 KB | |
| v0.22.2.tar.gz | 0001128517 1.08 MB |
Revision 112 (latest revision is 238)
Eric Schirra (ecsos)
committed
(revision 112)
- update to 0.22.2
* Fixed
- A type error introduced in 0.22.1 that would occur during
challenge cleanup when a Certbot plugin raises an exception
while trying to complete the challenge was fixed.
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:
certbot
More details about these changes can be found on our GitHub
repo: https://github.com/certbot/certbot/milestone/53?closed=1
- changes from 0.22.1
* Changed
- The ACME server used with Certbot's --dry-run and --staging
flags is now Let's Encrypt's ACMEv2 staging server which
allows people to also test ACMEv2 features with these flags.
* Fixed
- The HTTP Content-Type header is now set to the correct value
during certificate revocation with new versions of the ACME
protocol.
- When using Certbot with Let's Encrypt's ACMEv2 server,
it would add a blank line to the top of chain.pem and between
the certificates in fullchain.pem for each lineage.
These blank lines have been removed.
- Resolved a bug that caused Certbot's --allow-subset-of-names
flag not to work.
- Fixed a regression in acme.client.Client that caused the
class to not work when it was initialized without
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.