1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
"""
The `~certbot_dns_desec.dns_desec` plugin automates the process of
completing a ``dns-01`` challenge (`~acme.challenges.DNS01`) by creating, and
subsequently removing, TXT records using the deSEC REST API.
Named Arguments
---------------
======================================== =====================================
``--dns-desec-credentials`` deSEC Remote API credentials_
INI file. (Required)
``--dns-desec-propagation-seconds`` The number of seconds to wait for DNS
to propagate before asking the ACME
server to verify the DNS record.
(Default: 120) # TODO default, needed?
======================================== =====================================
Credentials
-----------
Use of this plugin requires a configuration file containing a deSEC DNS API
access token obtained from the deSEC website.
.. code-block:: ini
:name: credentials.ini
:caption: Example credentials file:
# deSEC API token used by Certbot
dns_desec_token = asdf
dns_desec_endpoint = https://localhost:8080
The path to this file can be provided interactively or using the
``--dns-desec-credentials`` command-line argument. Certbot records the path
to this file for use during renewal, but does not store the file's contents.
.. caution::
You should protect these API credentials as you would a password. Users who
can read this file can use these credentials to issue API calls on
your behalf. Users who can cause Certbot to run using these credentials can
complete a ``dns-01`` challenge to acquire new certificates or revoke
existing certificates for associated domains, even if those domains aren't
being managed by this server.
Certbot will emit a warning if it detects that the credentials file can be
accessed by other users on your system. The warning reads "Unsafe permissions
on credentials configuration file", followed by the path to the credentials
file. This warning will be emitted each time Certbot uses the credentials file,
including for renewal, and cannot be silenced except by addressing the issue
(e.g., by using a command like ``chmod 600`` to restrict access to the file).
Examples
--------
.. code-block:: bash
:caption: To acquire a certificate for ``example.com``
certbot certonly \\
--dns-desec \\
--dns-desec-credentials ~/.secrets/certbot/desec.ini \\
-d example.com
.. code-block:: bash
:caption: To acquire a single certificate for both ``example.com`` and
``www.example.com``
certbot certonly \\
--dns-desec \\
--dns-desec-credentials ~/.secrets/certbot/desec.ini \\
-d example.com \\
-d www.example.com
.. code-block:: bash
:caption: To acquire a certificate for ``example.com``, waiting 240 seconds
for DNS propagation
certbot certonly \\
--dns-desec \\
--dns-desec-credentials ~/.secrets/certbot/desec.ini \\
--dns-desec-propagation-seconds 240 \\ # TODO
-d example.com
"""
|
