From ce28cbc0d8bd907982212f4963b3a3e48215f688 Mon Sep 17 00:00:00 2001 From: Pierre Riteau <pierre@stackhpc.com> Date: Tue, 6 Dec 2022 11:39:23 +0100 Subject: [PATCH] docs: Fix reference to Libvirt TLS Change-Id: I2df1eff4e9eda42127db5b0bfed4f84b6955c763 --- doc/source/reference/compute/libvirt-guide.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/reference/compute/libvirt-guide.rst b/doc/source/reference/compute/libvirt-guide.rst index 013210c04..414c32ceb 100644 --- a/doc/source/reference/compute/libvirt-guide.rst +++ b/doc/source/reference/compute/libvirt-guide.rst @@ -29,7 +29,7 @@ authenticated with SASL. This should not be considered as providing a secure, encrypted channel, since the username/password SASL mechanisms available for TCP are no longer considered cryptographically secure. However, it does at least provide some authentication for the libvirt API. For a more secure -encrypted channel, use :ref`libvirt TLS <libvirt-tls>`. +encrypted channel, use :ref:`libvirt TLS <libvirt-tls>`. SASL is enabled according to the ``libvirt_enable_sasl`` flag, which defaults to ``true``. @@ -93,7 +93,7 @@ to ``true`` will cause the Docker volumes to be removed. A future extension could support migration of existing VMs, but this is currently out of scope. -.. libvirt-tls: +.. _libvirt-tls: Libvirt TLS =========== -- GitLab