Before upgrading, it is advised to read the :doc:`changelog/index`.
When upgrading several versions, please read **all** notes applying to the upgrade.
+5.4.0 to master
+---------------
+
+Changed Settings
+^^^^^^^^^^^^^^^^
+The :ref:`incoming-ws-config` YAML struct has been extended to be able to specify an encrypted PKCS12 file to configure TLS key and certificate chain.
+
+
5.1.10, 5.2.8 and 5.3.5
-----------------------
- The :ref:`setting-yaml-recordcache.max_entry_size` setting has been introduced to limit the maximum size of a stored record set.
- The :ref:`setting-yaml-packetcache.max_entry_size` setting has been introduced to limit the maximum size of a packet cache entry.
-5.3.0 to master
+5.3.0 to 5.4.0
---------------
New Settings
- example.com
- example.net
+Description of YAML syntax for additional structured types
+----------------------------------------------------------
+
ForwardingCatalogZone
^^^^^^^^^^^^^^^^^^^^^
As of version 5.2.0, a forwarding catalog zone entry is defined as:
addresses: [] Sequence of SocketAddress
tls:
- certificates: file containing full certificate chain in PEM format
+ certificates: file containing full certificate chain in PEM format or (since version 5.5.0) a PKCS12 file
key: file containing private key in PEM format
-
+ password: the password used to decrypt a PKCS12 file (since version 5.5.0)
A :ref:`setting-yaml-webservice.listen` section contains a sequence of `IncomingWSConfig`_, for example:
If no ``tls`` section is present, plaintext ``http`` connections are accepted on the listed addresses.
-If a ``tls`` section is present, clients are required to use ``https`` to contact any of the address-port combinations listen in addresses. At the moment it is not possible to list additional properties of the TLS listener and encrypted key files cannot be used.
+If a ``tls`` section is present, clients are required to use ``https`` to contact any of the address-port combinations listen in addresses.
+
+If both the ``certificate`` and the ``key`` fields are set, the values specify unencrypted PEM files.
+The ``password`` field is ignored in that case.
+
+Starting with version 5.5.0, if the ``key`` field is not set but the ``certificate`` and ``password`` fields are set, the listed file is assumed to be an encrypted PKCS12 (also known as pfx) file containing both a key and the certificate chain.
+
+At the moment it is not possible to list additional properties of the TLS listener.
OutgoingTLSConfiguration
^^^^^^^^^^^^^^^^^^^^^^^^