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.

217 lines
8.3 KiB

5 years ago
4 years ago
4 years ago
4 years ago
4 years ago
5 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. - Configuration files cannot be loaded more than one time, which prevents infinite recursion.
  13. ### Changed
  14. - Certificates are now allowed to share the same name if their respective key type is different.
  15. ## [0.14.0] - 2020-10-27
  16. ### Added
  17. - Add proxy support through the `HTTP_PROXY`, `HTTPS_PROXY` and `NO_PROXY` environment variables.
  18. - Allow to specify a unique name for each certificate.
  19. ### Changed
  20. - The minimal required Rust version is 1.42.0.
  21. ## [0.13.0] - 2020-10-10
  22. ### Added
  23. - 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.
  24. - At compilation, it is now possible to statically link OpenSSL using the `openssl_vendored` feature.
  25. - In the Makefile, it is now possible to specify which target triple to build for.
  26. ## [0.12.0] - 2020-09-26
  27. ### Added
  28. - Some subject attributes can now be specified.
  29. - Support for NIST P-521 certificates and account keys.
  30. ### Fixed
  31. - Support for Let's Encrypt non-standard account creation object.
  32. ## [0.11.0] - 2020-09-19
  33. ### Added
  34. - The `contacts` account configuration field has been added.
  35. - External account binding.
  36. ### Changed
  37. - The `email` account configuration field has been removed. In replacement, use the `contacts` field.
  38. - Accounts now have their own hooks and environment.
  39. - Accounts are now stored in a single binary file.
  40. ### Fixed
  41. - ACMEd can now build on platforms with a `time_t` not defined as an `i64`.
  42. - The Makefile is now fully works on FreeBSD.
  43. ## [0.10.0] - 2020-08-27
  44. ### Added
  45. - The account key type and signature algorithm can now be specified in the configuration using the `key_type` and `signature_algorithm` parameters.
  46. - 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.
  47. - It is now possible to specify IP identifiers (RFC 8738) using the `ip` parameter instead of the `dns` one.
  48. - 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.
  49. - Globing is now supported for configuration files inclusion.
  50. - The CSR's digest algorithm can now be specified using the `csr_digest` parameter.
  51. ### Changed
  52. - In the certificate configuration, the `domains` field has been renamed `identifiers`.
  53. - The `algorithm` certificate configuration field has been renamed `key_type`.
  54. - The `algorithm` hook template variable has been renamed `key_type`.
  55. - The `domain` hook template variable has been renamed `identifier`.
  56. - The default hooks have been updated.
  57. ### Fixed
  58. - The Makefile now works on FreeBSD. It should also work on other BSD although it has not been tested.
  59. ## [0.9.0] - 2020-08-01
  60. ### Added
  61. - System users and groups can now be specified by name in addition to uid/gid.
  62. ### Changed
  63. - The HTTP(S) part is now handled by `attohttpc` instead of `reqwest`.
  64. ### Fixed
  65. - In tacd, the `--acme-ext-file` parameter is now in conflict with `acme-ext` instead of itself.
  66. ## [0.8.0] - 2020-06-12
  67. ### Changed
  68. - The HTTP(S) part is now handled by `reqwest` instead of `http_req`.
  69. ## Fixed
  70. - `make install` now work with the busybox toolchain.
  71. ## [0.7.0] - 2020-03-12
  72. ### Added
  73. - Wildcard certificates are now supported. In the file name, the `*` is replaced by `_`.
  74. - Internationalized domain names are now supported.
  75. ### Changed
  76. - 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.
  77. ### Fixed
  78. - In the directory, the `externalAccountRequired` field is now a boolean instead of a string.
  79. ## [0.6.1] - 2019-09-13
  80. ### Fixed
  81. - A race condition when requesting multiple certificates on the same non-existent account has been fixed.
  82. - The `foregroung` option has been renamed `foreground`.
  83. ## [0.6.0] - 2019-06-05
  84. ### Added
  85. - Hooks now have the optional `allow_failure` field.
  86. - In hooks, the `stdin_str` has been added in replacement of the previous `stdin` behavior.
  87. - HTTPS request rate limits.
  88. ### Changed
  89. - Certificates are renewed in parallel.
  90. - Hooks are now cleaned right after the current challenge has been validated instead of after the certificate's retrieval.
  91. - In hooks, the `stdin` field now refers to the path of the file that should be written into the hook's standard input.
  92. - The logging format has been re-written.
  93. ### Fixed
  94. - The http-01-echo hook now correctly sets the file's access rights
  95. ## [0.5.0] - 2019-05-09
  96. ### Added
  97. - ACMEd now displays a warning when the server indicates an error in an order or an authorization.
  98. - A configuration file can now include several other files.
  99. - Hooks have access to environment variables.
  100. - In the configuration, the global section, certificates and domains can define environment variables for the hooks.
  101. - tacd is now able to listen on a unix socket.
  102. ## [0.4.0] - 2019-05-08
  103. ### Added
  104. - Man pages.
  105. - The project can now be built and installed using `make`.
  106. - The post-operation hooks now have access to the `is_success` template variable.
  107. - Challenge hooks now have the `is_clean_hook` template variable.
  108. - An existing certificate will be renewed if more domains have been added in the configuration.
  109. ### Changed
  110. - Unknown configuration fields are no longer tolerated.
  111. ### Removed
  112. - In challenge hooks, the `algorithm` template variable has been removed.
  113. ### Fixed
  114. - In some cases, ACMEd was unable to parse a certificate's expiration date.
  115. ## [0.3.0] - 2019-04-30
  116. ### Added
  117. - tacd, the TLS-ALPN-01 validation daemon.
  118. - An account object has been added in the configuration.
  119. - In the configuration, hooks now have a mandatory `type` variable.
  120. - It is now possible to declare hooks to clean after the challenge validation hooks.
  121. - The CLI `--root-cert` option has been added.
  122. - 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.
  123. - 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.
  124. ### Changed
  125. - In the configuration, the `email` certificate field has been replaced by the `account` field which matches an account object.
  126. - The format of the `domain` configuration variable has changed and now includes the challenge type.
  127. - The `token` challenge hook variable has been renamed `file_name`.
  128. - 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`.
  129. - The logs has been purged from many useless debug and trace entries.
  130. ### Removed
  131. - The DER storage format has been removed.
  132. - The `challenge` certificate variables has been removed.
  133. ## [0.2.1] - 2019-03-30
  134. ### Changed
  135. - The bug that prevented from requesting more than two certificates has been fixed.
  136. ## [0.2.0] - 2019-03-27
  137. ### Added
  138. - The `kp_reuse` flag allow to reuse a key pair instead of creating a new one at each renewal.
  139. - It is now possible to define hook groups that can reference either hooks or other hook groups.
  140. - 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`).
  141. - It is now possible to send logs either to syslog or stderr using the `--to-syslog` and `--to-stderr` arguments.
  142. ### Changed
  143. - `post_operation_hook` has been renamed `post_operation_hooks`.
  144. - By default, logs are now sent to syslog instead of stderr.
  145. - The process is now daemonized by default. It is possible to still run it in the foreground using the `--foregroung` flag.