From eb959c32be1d91b810cbd398d4201b94de8c8aae Mon Sep 17 00:00:00 2001 From: felixfontein Date: Sat, 28 Dec 2024 16:09:17 +0000 Subject: [PATCH] deploy: ddbcf49868a687f5ee03d5e66002bdae3c23b7b9 --- branch/main/acme_certificate_module.html | 2 +- branch/main/openssl_privatekey_module.html | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/branch/main/acme_certificate_module.html b/branch/main/acme_certificate_module.html index 62d89caf..2dcb263d 100644 --- a/branch/main/acme_certificate_module.html +++ b/branch/main/acme_certificate_module.html @@ -204,7 +204,7 @@ see

  • Create and renew SSL/TLS certificates with a CA supporting the ACME protocol, such as Let’s Encrypt or Buypass. The current implementation supports the http-01, dns-01 and tls-alpn-01 challenges.

  • To use this module, it has to be executed twice. Either as two different tasks in the same run or during two runs. Note that the output of the first run needs to be recorded and passed to the second run as the module argument data.

    • -

  • Between these two tasks you have to fulfill the required steps for the chosen challenge by whatever means necessary. For http-01 that means creating the necessary challenge file on the destination webserver. For dns-01 the necessary dns record has to be created. For tls-alpn-01 the necessary certificate has to be created and served. It is not the responsibility of this module to perform these steps.

    • +

  • Between these two tasks you have to fulfill the required steps for the chosen challenge by whatever means necessary. For http-01 that means creating the necessary challenge file on the destination webserver. For dns-01 the necessary DNS record has to be created. For tls-alpn-01 the necessary certificate has to be created and served. It is not the responsibility of this module to perform these steps.

  • For details on how to fulfill these challenges, you might have to read through the main ACME specification and the TLS-ALPN-01 specification. Also, consider the examples provided for this module.

  • The module includes experimental support for IP identifiers according to the RFC 8738.

    • diff --git a/branch/main/openssl_privatekey_module.html b/branch/main/openssl_privatekey_module.html index d7cef5c5..0a24582b 100644 --- a/branch/main/openssl_privatekey_module.html +++ b/branch/main/openssl_privatekey_module.html @@ -202,7 +202,7 @@ see

  • Keys are generated in PEM format.

  • One can generate RSA, DSA, ECC or EdDSA private keys.

    • -

  • Please note that the module regenerates private keys if they do not match the module’s options. In particular, if you provide another passphrase (or specify none), change the keysize, etc., the private key will be regenerated. If you are concerned that this could overwrite your private key, consider using the backup option.

    • +

  • Please note that the module regenerates private keys if they do not match the module’s options. In particular, if you provide another passphrase (or specify none), change the keysize, and so on, the private key will be regenerated. If you are concerned that this could overwrite your private key, consider using the backup option.

  • The default mode for the private key file will be 0600 if mode is not explicitly set.

  • This module allows one to (re)generate OpenSSL private keys.

    • @@ -407,7 +407,7 @@ see added in community.crypto 1.0.0

    If set to true, will return the (current or generated) private key’s content as privatekey.

    -

    Note that especially if the private key is not encrypted, you have to make sure that the returned value is treated appropriately and not accidentally written to logs etc.! Use with care!

    +

    Note that especially if the private key is not encrypted, you have to make sure that the returned value is treated appropriately and not accidentally written to logs, and so on! Use with care!

    Use Ansible’s no_log task option to avoid the output being shown. See also https://docs.ansible.com/ansible/latest/reference_appendices/faq.html#how-do-i-keep-secret-data-in-my-playbook.

    Choices: