On Sat, Feb 13, 2021 at 08:36:29AM +0200, Ville Skyttä wrote:
> Signed-off-by: Ville Skyttä
> ---
> docs/tlscerts.html.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/docs/tlscerts.html.in b/docs/tlscerts.html.in
> index 8a74311682..22fc054801 100644
> --- a/docs/tlscerts.html.in
> +++ b/docs/tlscerts.html.in
> @@ -125,7 +125,7 @@ of the server and clients. There are two distinct checks
> involved:
> server. Checking done by client by matching the certificate that
> the server sends to the server's hostname. May be disabled by adding
> ?no_verify=1 to the
> -remote URI.
> +remote URI.
This is not the only broken reference on that page - I'll squash the following
in before pushing:
diff --git a/docs/tlscerts.html.in b/docs/tlscerts.html.in
index 22fc054801..5b7a5f56e4 100644
--- a/docs/tlscerts.html.in
+++ b/docs/tlscerts.html.in
@@ -132,3 +132,3 @@ connecting. This can be done based on client's IP address,
or on
client's IP address and client's certificate. Checking done by the
-server. May be enabled and disabled in the libvirtd.conf file.
+server. May be enabled and disabled in the libvirtd.conf file.
@@ -144,3 +144,3 @@ issues by your own CA. Follow the instructions in the next
section.
-Be aware that the default
+Be aware that the default
configuration for libvirtd allows any client to connect provided
@@ -238,3 +238,3 @@ include the SAN fields.
In the example below, clients will be connecting to the
-server using a URI of
+server using a URI of
qemu://compute1.libvirt.org/system, so the CN
Reviewed-by: Erik Skultety
