diff options
| author | Christian Breunig <christian@breunig.cc> | 2024-01-05 22:27:45 +0100 |
|---|---|---|
| committer | Christian Breunig <christian@breunig.cc> | 2024-01-08 21:11:13 +0100 |
| commit | f8f51939ae5ad852563cc69c4e2c8c2717318c9c (patch) | |
| tree | 9d4639f892f09d1fa1dd3f5f4043661da4085ebf /src/etc/systemd/system/certbot.service.d/10-override.conf | |
| parent | 3f64c00c892b12673c80ddf450334848476f5249 (diff) | |
| download | vyos-1x-f8f51939ae5ad852563cc69c4e2c8c2717318c9c.tar.gz vyos-1x-f8f51939ae5ad852563cc69c4e2c8c2717318c9c.zip | |
pki: T5886: add support for ACME protocol (LetsEncrypt)
The "idea" of this PR is to add new CLI nodes under the pki subsystem to
activate ACME for any given certificate.
vyos@vyos# set pki certificate NAME acme
Possible completions:
+ domain-name Domain Name
email Email address to associate with certificate
listen-address Local IPv4 addresses to listen on
rsa-key-size Size of the RSA key (default: 2048)
url Remote URL (default:
https://acme-v02.api.letsencrypt.org/directory)
Users choose if the CLI based custom certificates are used
set pki certificate EXAMPLE acme certificate <base64>
or if it should be generated via ACME.
The ACME server URL defaults to LetsEncrypt but can be changed to their staging
API for testing to not get blacklisted.
set pki certificate EXAMPLE acme url https://acme-staging-v02.api.letsencrypt.org/directory
Certificate retrieval has a certbot --dry-run stage in verify() to see if it
can be generated.
After successful generation, the certificate is stored in under
/config/auth/letsencrypt. Once a certificate is referenced in the CLI (e.g. set
interfaces ethernet eth0 eapol certificate EXAMPLE) we call
vyos.config.get_config_dict() which will (if with_pki=True is set) blend in the
base64 encoded certificate into the JSON data structure normally used when
using a certificate set by the CLI.
Using this "design" does not need any change to any other code referencing the
PKI system, as the base64 encoded certificate is already there.
certbot renewal will call the PKI python script to trigger dependency updates.
(cherry picked from commit b8db1a9d7baf91b70c1b735e58710f1e2bc9fc7a)
# Conflicts:
# debian/control
Diffstat (limited to 'src/etc/systemd/system/certbot.service.d/10-override.conf')
| -rw-r--r-- | src/etc/systemd/system/certbot.service.d/10-override.conf | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/src/etc/systemd/system/certbot.service.d/10-override.conf b/src/etc/systemd/system/certbot.service.d/10-override.conf new file mode 100644 index 000000000..542f77eb2 --- /dev/null +++ b/src/etc/systemd/system/certbot.service.d/10-override.conf @@ -0,0 +1,7 @@ +[Unit] +After= +After=vyos-router.service + +[Service] +ExecStart= +ExecStart=/usr/bin/certbot renew --config-dir /config/auth/letsencrypt --no-random-sleep-on-renew --post-hook "/usr/libexec/vyos/vyos-certbot-renew-pki.sh" |