You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

288 lines
10 KiB

5 years ago
2 years ago
2 years ago
2 years ago
2 years ago
3 years ago
3 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
4 years ago
5 years ago
5 years ago
5 years ago
6 years ago
6 years ago
6 years ago
6 years ago
6 years ago
  1. [//]: # (Copyright 2019-2020 Rodolphe Bréard <rodolphe@breard.tf>)
  2. [//]: # (Copying and distribution of this file, with or without modification,)
  3. [//]: # (are permitted in any medium without royalty provided the copyright)
  4. [//]: # (notice and this notice are preserved. This file is offered as-is,)
  5. [//]: # (without any warranty.)
  6. # Changelog
  7. All notable changes to this project will be documented in this file.
  8. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
  9. and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
  10. ## [Unreleased]
  11. ### Fixed
  12. - ACMEd no longer crashes when the `random_early_renew` parameter is set to zero (GitHub bug #102).
  13. ### Changed
  14. - The minimum supported Rust version (MSRV) is now 1.65.
  15. - Manual (and badly designed) threads have been replaced by async.
  16. - Randomized early delay, for spacing out renewals when dealing with a lot of certificates.
  17. - Replaced the template engine TinyTemplate with MiniJinja.
  18. ## [0.21.0] - 2022-12-19
  19. ### Fixed
  20. - The JWK representation of ECDSA keys now have their coordinates padded.
  21. ### Changed
  22. - The minimal required Rust version is now 1.60.
  23. ## [0.20.0] - 2022-05-08
  24. ### Added
  25. - The `--no-pid-file` argument has been added to ACMEd and tacd.
  26. ### Fixed
  27. - An invalid reference in the command line arguments has been fixed.
  28. - Some missing file path in log messages has been added.
  29. - The calculation of the certificate's expiration delay does no longer break compilation on some systems.
  30. ## [0.19.0] - 2022-04-17
  31. ### Added
  32. - The `acmed@user.service` systemd unit configuration has been added as an alternative to the `acmed.service` unit.
  33. ### Changed
  34. - The minimal required Rust version is now 1.54.
  35. ## [0.18.0] - 2021-06-13
  36. ### Added
  37. - Add support for Ed25519 and Ed448 account keys and certificates.
  38. - In addition to `restart`, the Polkit rule also allows the `reload`, `try-restart`, `reload-or-restart` and `try-reload-or-restart` verbs.
  39. ## [0.17.0] - 2021-05-04
  40. ### Added
  41. - Allow the configuration of some default values at compile time using environment variables.
  42. ### Changed
  43. - The template engine has been changed in favor of TinyTemplate, which has a different syntax than the previous one.
  44. - The default account directory now is `/var/lib/acmed/accounts`.
  45. - The default certificates and private keys directory now is `/var/lib/acmed/certs`.
  46. - The default for volatile runtime data now is `/run`.
  47. ## [0.16.0] - 2020-11-11
  48. ### Added
  49. - The `pkcs9_email_address`, `postal_address` and `postal_code` subject attributes has been added.
  50. ### Changed
  51. - The `friendly_name` and `pseudonym` subject attributes has been removed.
  52. - The `street_address` subject attribute has been renamed `street`.
  53. ## [0.15.0] - 2020-11-03
  54. ### Added
  55. - The names of both the certificate file and the associated private key can now be configured.
  56. ### Fixed
  57. - Configuration files cannot be loaded more than one time, which prevents infinite recursion.
  58. ### Changed
  59. - Certificates are now allowed to share the same name if their respective key type is different.
  60. ## [0.14.0] - 2020-10-27
  61. ### Added
  62. - Add proxy support through the `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables.
  63. - Allow to specify a unique name for each certificate.
  64. ### Changed
  65. - The minimal required Rust version is 1.42.0.
  66. ## [0.13.0] - 2020-10-10
  67. ### Added
  68. - In the configuration, `root_certificates` has been added to the `global` and `endpoint` sections as an array of strings representing the path to root certificate files.
  69. - At compilation, it is now possible to statically link OpenSSL using the `openssl_vendored` feature.
  70. - In the Makefile, it is now possible to specify which target triple to build for.
  71. ## [0.12.0] - 2020-09-26
  72. ### Added
  73. - Some subject attributes can now be specified.
  74. - Support for NIST P-521 certificates and account keys.
  75. ### Fixed
  76. - Support for Let's Encrypt non-standard account creation object.
  77. ## [0.11.0] - 2020-09-19
  78. ### Added
  79. - The `contacts` account configuration field has been added.
  80. - External account binding.
  81. ### Changed
  82. - The `email` account configuration field has been removed. In replacement, use the `contacts` field.
  83. - Accounts now have their own hooks and environment.
  84. - Accounts are now stored in a single binary file.
  85. ### Fixed
  86. - ACMEd can now build on platforms with a `time_t` not defined as an `i64`.
  87. - The Makefile is now fully works on FreeBSD.
  88. ## [0.10.0] - 2020-08-27
  89. ### Added
  90. - The account key type and signature algorithm can now be specified in the configuration using the `key_type` and `signature_algorithm` parameters.
  91. - The delay to renew a certificate before its expiration date can be specified in the configuration using the `renew_delay` parameter at either the certificate, endpoint and global level.
  92. - It is now possible to specify IP identifiers (RFC 8738) using the `ip` parameter instead of the `dns` one.
  93. - The hook templates of type `challenge-*` have a new `identifier_tls_alpn` field which contains, if available, the identifier in a form that is suitable to the TLS ALPN challenge.
  94. - Globing is now supported for configuration files inclusion.
  95. - The CSR's digest algorithm can now be specified using the `csr_digest` parameter.
  96. ### Changed
  97. - In the certificate configuration, the `domains` field has been renamed `identifiers`.
  98. - The `algorithm` certificate configuration field has been renamed `key_type`.
  99. - The `algorithm` hook template variable has been renamed `key_type`.
  100. - The `domain` hook template variable has been renamed `identifier`.
  101. - The default hooks have been updated.
  102. ### Fixed
  103. - The Makefile now works on FreeBSD. It should also work on other BSD although it has not been tested.
  104. ## [0.9.0] - 2020-08-01
  105. ### Added
  106. - System users and groups can now be specified by name in addition to uid/gid.
  107. ### Changed
  108. - The HTTP(S) part is now handled by `attohttpc` instead of `reqwest`.
  109. ### Fixed
  110. - In tacd, the `--acme-ext-file` parameter is now in conflict with `acme-ext` instead of itself.
  111. ## [0.8.0] - 2020-06-12
  112. ### Changed
  113. - The HTTP(S) part is now handled by `reqwest` instead of `http_req`.
  114. ## Fixed
  115. - `make install` now work with the busybox toolchain.
  116. ## [0.7.0] - 2020-03-12
  117. ### Added
  118. - Wildcard certificates are now supported. In the file name, the `*` is replaced by `_`.
  119. - Internationalized domain names are now supported.
  120. ### Changed
  121. - The PID file is now always written whether or not ACMEd is running in the foreground. Previously, it was written only when running in the background.
  122. ### Fixed
  123. - In the directory, the `externalAccountRequired` field is now a boolean instead of a string.
  124. ## [0.6.1] - 2019-09-13
  125. ### Fixed
  126. - A race condition when requesting multiple certificates on the same non-existent account has been fixed.
  127. - The `foregroung` option has been renamed `foreground`.
  128. ## [0.6.0] - 2019-06-05
  129. ### Added
  130. - Hooks now have the optional `allow_failure` field.
  131. - In hooks, the `stdin_str` has been added in replacement of the previous `stdin` behavior.
  132. - HTTPS request rate limits.
  133. ### Changed
  134. - Certificates are renewed in parallel.
  135. - Hooks are now cleaned right after the current challenge has been validated instead of after the certificate's retrieval.
  136. - In hooks, the `stdin` field now refers to the path of the file that should be written into the hook's standard input.
  137. - The logging format has been re-written.
  138. ### Fixed
  139. - The http-01-echo hook now correctly sets the file's access rights
  140. ## [0.5.0] - 2019-05-09
  141. ### Added
  142. - ACMEd now displays a warning when the server indicates an error in an order or an authorization.
  143. - A configuration file can now include several other files.
  144. - Hooks have access to environment variables.
  145. - In the configuration, the global section, certificates and domains can define environment variables for the hooks.
  146. - tacd is now able to listen on a unix socket.
  147. ## [0.4.0] - 2019-05-08
  148. ### Added
  149. - Man pages.
  150. - The project can now be built and installed using `make`.
  151. - The post-operation hooks now have access to the `is_success` template variable.
  152. - Challenge hooks now have the `is_clean_hook` template variable.
  153. - An existing certificate will be renewed if more domains have been added in the configuration.
  154. ### Changed
  155. - Unknown configuration fields are no longer tolerated.
  156. ### Removed
  157. - In challenge hooks, the `algorithm` template variable has been removed.
  158. ### Fixed
  159. - In some cases, ACMEd was unable to parse a certificate's expiration date.
  160. ## [0.3.0] - 2019-04-30
  161. ### Added
  162. - tacd, the TLS-ALPN-01 validation daemon.
  163. - An account object has been added in the configuration.
  164. - In the configuration, hooks now have a mandatory `type` variable.
  165. - It is now possible to declare hooks to clean after the challenge validation hooks.
  166. - The CLI `--root-cert` option has been added.
  167. - Failure recovery: HTTPS requests rejected by the server that are recoverable, like the badNonce error, are now retried several times before being considered a hard failure.
  168. - The TLS-ALPN-01 challenge is now supported. The proof is a string representation of the acmeIdentifier extension. The self-signed certificate itself has to be built by a hook.
  169. ### Changed
  170. - In the configuration, the `email` certificate field has been replaced by the `account` field which matches an account object.
  171. - The format of the `domain` configuration variable has changed and now includes the challenge type.
  172. - The `token` challenge hook variable has been renamed `file_name`.
  173. - The `challenge_hooks`, `post_operation_hooks`, `file_pre_create_hooks`, `file_post_create_hooks`, `file_pre_edit_hooks` and `file_post_edit_hooks` certificate variables has been replaced by `hooks`.
  174. - The logs has been purged from many useless debug and trace entries.
  175. ### Removed
  176. - The DER storage format has been removed.
  177. - The `challenge` certificate variables has been removed.
  178. ## [0.2.1] - 2019-03-30
  179. ### Changed
  180. - The bug that prevented from requesting more than two certificates has been fixed.
  181. ## [0.2.0] - 2019-03-27
  182. ### Added
  183. - The `kp_reuse` flag allow to reuse a key pair instead of creating a new one at each renewal.
  184. - It is now possible to define hook groups that can reference either hooks or other hook groups.
  185. - Hooks can be defined when before and after a file is created or edited (`file_pre_create_hooks`, `file_post_create_hooks`, `file_pre_edit_hooks` and `file_post_edit_hooks`).
  186. - It is now possible to send logs either to syslog or stderr using the `--to-syslog` and `--to-stderr` arguments.
  187. ### Changed
  188. - `post_operation_hook` has been renamed `post_operation_hooks`.
  189. - By default, logs are now sent to syslog instead of stderr.
  190. - The process is now daemonized by default. It is possible to still run it in the foreground using the `--foregroung` flag.