Certificats Let's Encrypt
Find a file
Brad Warren deb3d035e3
require ssl vhosts for HSTS and OCSP stapling (#10455)
this is the first part of the nginx refactoring work i wanted to do.
ohemorange, if this conflicts with your work on updating our nginx ssl
config, please feel free to either ignore this for now or point me to
your branch after merging this and i can fix up any merge conflicts
myself like i previously offered

the main thing this PR does is create a new choose_or_make_vhosts
function with the current choose_vhosts behavior and makes choose_vhosts
only return existing ssl vhosts which i think is the behavior we want
when setting up HSTS or OCSP stapling. [this is what we do in
apache](867b499f9b/certbot-apache/src/certbot_apache/_internal/configurator.py (L1795-L1829)),
enabling HSTS or OCSP stapling on an HTTP vhost seems wrong/dangerous,
and since we don't have cert and key information in these [enhance
calls](867b499f9b/certbot/src/certbot/interfaces.py (L255)),
any SSL vhost we create will be left with snakeoil certs which also
seems very wrong

of course, this simple change to certbot-nginx's prod code required many
changes to its tests. the config file for headers.com was introduced
[here](https://github.com/certbot/certbot/pull/6068) specifically for
testing HSTS so i added the SSL configuration it needs to make work with
the choose_vhost changes. that then broke the IP tests for headers.com
that were added in https://github.com/certbot/certbot/pull/10145/ so i
created a new no-listens.com vhost for testing that

if this is merged, my plan in the next PR or two is to:

1. since choose_or_make_vhosts is now always called with
create_if_no_match=True in prod code, i plan to remove that variable,
make that the default behavior of the function, and fix up tests
2. then, since choose_or_make_vhosts is only called in deploy_cert, i
plan to pass the cert and key to it so it can be used in
_make_server_ssl instead of the dummy certs currently being used there

i could do more of this in this PR if you want ohemorange, but i figured
it rarely hurts to break things up especially when the code is kind of
tricky like it is (to me) here
2025-09-17 14:23:32 -07:00
.azure-pipelines remove python 3.9 support (#10406) 2025-08-12 17:49:02 +00:00
.github Add towncrier for automatic changelog generation (#10379) 2025-07-31 07:12:56 -07:00
acme Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-apache Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-ci Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-compatibility-test Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-cloudflare Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-digitalocean Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-dnsimple Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-dnsmadeeasy Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-gehirn Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-google Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-linode Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-luadns Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-nsone Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-ovh Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-rfc2136 Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-route53 Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-dns-sakuracloud Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
certbot-nginx require ssl vhosts for HSTS and OCSP stapling (#10455) 2025-09-17 14:23:32 -07:00
letsencrypt-auto-source Restore le-auto, which should not be modified (#10351) 2025-06-24 21:07:55 +00:00
letstest Bump version to 5.1.0 2025-09-02 08:47:05 -07:00
newsfragments require ssl vhosts for HSTS and OCSP stapling (#10455) 2025-09-17 14:23:32 -07:00
snap modify pyvenv.cfg instead of PYTHONPATH (#10384) 2025-08-01 11:55:38 -07:00
tests Rewrite lock_test.py (#9614) 2023-03-15 12:54:20 -07:00
tools stop running setup.py and switch to python -m build (#10442) 2025-08-22 11:03:00 -07:00
.coveragerc rewrite coverage tests (#9669) 2023-04-17 13:01:00 -07:00
.dockerignore Cleanup venv scripts (#8629) 2021-02-03 12:03:09 -08:00
.editorconfig Added an .editorconfig file. (#8297) 2020-09-19 11:39:13 +02:00
.gitattributes Merge pull request #2136 from tboegi/gitattributes_eol_overrideses_auto 2016-06-16 14:29:39 -07:00
.gitignore Drop in uv for pip (#10428) 2025-08-18 13:17:02 -07:00
.isort.cfg Add --use-pep517 flag to pip to silence warning in tools/venv.py, and switch codebase to src-layout (#10249) 2025-04-11 19:30:33 +00:00
.pylintrc Upgrade the pinned version of pylint (#9839) 2023-11-15 09:52:37 +01:00
AUTHORS.md Remove the dependency on pytz (#10350) 2025-07-28 08:00:16 -07:00
CHANGELOG.md Refactor certbot/ and certbot/tests/ to use the same structure as the other packages (#7544) 2019-11-25 14:28:05 -08:00
CODE_OF_CONDUCT.md Added a CODE_OF_CONDUCT.md file so Github doesn't complain 2019-04-17 11:36:26 -07:00
CONTRIBUTING.md [DOCS] Update CONTRIBUTING.md (#10220) 2025-03-04 19:01:39 -08:00
LICENSE.txt More stray ncrypt reference cleanup 2016-04-14 17:04:23 -07:00
linter_plugin.py Run ruff to fix test errors (#10398) 2025-08-07 22:10:02 +00:00
mypy.ini Run mypy with --strict on modules that are ready for it (#10166) 2025-01-30 23:11:31 +00:00
pytest.ini fixup pytest.ini, out var, and add changelog 2025-08-28 09:33:37 -07:00
README.rst Refactor certbot/ and certbot/tests/ to use the same structure as the other packages (#7544) 2019-11-25 14:28:05 -08:00
ruff.toml use pep585 types everywhere and add a test (#10414) 2025-08-12 16:56:45 -07:00
SECURITY.md [REPO] Update SECURITY.md (#10253) 2025-05-06 10:57:50 -07:00
towncrier.toml Add towncrier for automatic changelog generation (#10379) 2025-07-31 07:12:56 -07:00
tox.ini Have oldest tests inherit environment from python tests (#10422) 2025-08-14 16:36:34 -07:00

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

.. This file contains a series of comments that are used to include sections of this README in other files. Do not modify these comments unless you know what you are doing. tag:intro-begin

|build-status|

.. |build-status| image:: https://img.shields.io/azure-devops/build/certbot/ba534f81-a483-4b9b-9b4e-a60bec8fee72/5/main
   :target: https://dev.azure.com/certbot/certbot/_build?definitionId=5
   :alt: Azure Pipelines CI status

.. image:: https://raw.githubusercontent.com/EFForg/design/master/logos/certbot/eff-certbot-lockup.png
  :width: 200
  :alt: EFF Certbot Logo

Certbot is part of EFFs effort to encrypt the entire Internet. Secure communication over the Web relies on HTTPS, which requires the use of a digital certificate that lets browsers verify the identity of web servers (e.g., is that really google.com?). Web servers obtain their certificates from trusted third parties called certificate authorities (CAs). Certbot is an easy-to-use client that fetches a certificate from Lets Encrypt—an open certificate authority launched by the EFF, Mozilla, and others—and deploys it to a web server.

Anyone who has gone through the trouble of setting up a secure website knows what a hassle getting and maintaining a certificate is. Certbot and Lets Encrypt can automate away the pain and let you turn on and manage HTTPS with simple commands. Using Certbot and Let's Encrypt is free.

.. _installation:

Getting Started
---------------
The best way to get started is to use our `interactive guide <https://certbot.eff.org>`_. It generates instructions based on your configuration settings. In most cases, youll need `root or administrator access <https://certbot.eff.org/faq/#does-certbot-require-root-administrator-privileges>`_ to your web server to run Certbot.

Certbot is meant to be run directly on your web server on the command line, not on your personal computer. If youre using a hosted service and dont have direct access to your web server, you might not be able to use Certbot. Check with your hosting provider for documentation about uploading certificates or using certificates issued by Lets Encrypt.

Contributing
------------

If you'd like to contribute to this project please read `Developer Guide
<https://certbot.eff.org/docs/contributing.html>`_.

This project is governed by `EFF's Public Projects Code of Conduct <https://www.eff.org/pages/eppcode>`_.

Links
=====

.. Do not modify this comment unless you know what you're doing. tag:links-begin

Documentation: https://certbot.eff.org/docs

Software project: https://github.com/certbot/certbot

Changelog: https://github.com/certbot/certbot/blob/main/certbot/CHANGELOG.md

For Contributors: https://certbot.eff.org/docs/contributing.html

For Users: https://certbot.eff.org/docs/using.html

Main Website: https://certbot.eff.org

Let's Encrypt Website: https://letsencrypt.org

Community: https://community.letsencrypt.org

ACME spec: `RFC 8555 <https://tools.ietf.org/html/rfc8555>`_

ACME working area in github (archived): https://github.com/ietf-wg-acme/acme

.. Do not modify this comment unless you know what you're doing. tag:links-end

.. Do not modify this comment unless you know what you're doing. tag:intro-end

.. Do not modify this comment unless you know what you're doing. tag:features-begin

Current Features
=====================

* Supports multiple web servers:

  - Apache 2.4+
  - nginx/0.8.48+
  - webroot (adds files to webroot directories in order to prove control of
    domains and obtain certificates)
  - standalone (runs its own simple webserver to prove you control a domain)
  - other server software via `third party plugins <https://certbot.eff.org/docs/using.html#third-party-plugins>`_

* The private key is generated locally on your system.
* Can talk to the Let's Encrypt CA or optionally to other ACME
  compliant services.
* Can get domain-validated (DV) certificates.
* Can revoke certificates.
* Supports ECDSA (default) and RSA certificate private keys.
* Can optionally install a http -> https redirect, so your site effectively
  runs https only.
* Fully automated.
* Configuration changes are logged and can be reverted.

.. Do not modify this comment unless you know what you're doing. tag:features-end