certbot formerly letsencrypt client for Lets Encrypt Certificates

Edit Package certbot
https://certbot.eff.org/

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.

Refresh
Refresh
Source Files
Filename Size Changed
README.SUSE 0000001749 1.71 KB
certbot-1.21.0.tar.gz 0001343180 1.28 MB
certbot-cli.ini.patch 0000001950 1.9 KB
certbot-fix_constants.patch 0000026515 25.9 KB
certbot-repoze.sphinx.autointerface.patch 0000000435 435 Bytes
certbot.changes 0000075643 73.9 KB
certbot.cron 0000000949 949 Bytes
certbot.rpmlintrc 0000000195 195 Bytes
certbot.spec 0000020043 19.6 KB
Revision 206 (latest revision is 238)
Eric Schirra's avatar Eric Schirra (ecsos) committed (revision 206)
- Update to 1.21.0
  * Added
    - Certbot will generate a web.config file on Windows in the challenge path
      when the webroot plugin is used, if one does not exist. This web.config file
      lets IIS serve challenge files while they do not have an extension.
  * Changed
    - We changed the PGP key used to sign the packages we upload to PyPI. Going
      forward, releases will be signed with one of three different keys. All of
      these keys are available on major key servers and signed by our previous PGP
      key. The fingerprints of these new keys are:
        o BF6BCFC89E90747B9A680FD7B6029E8500F7DB16
        o 86379B4F0AF371B50CD9E5FF3402831161D1D280
        o 20F201346BF8F3F455A73F9A780CC99432A28621
Comments 2

Yunhe Guo's avatar

Does it make sense to use systemd instead of cron? It will be easier to enable/disable in YaST and monitor errors.


Eric Schirra's avatar

I am not a friend of systemd. And certainly not from systemd cron. Sorry.

openSUSE Build Service is sponsored by