External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 13:45:38 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Move 'tlscerts' page to 'kbase/'

Browse Source 
Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Pavel Hrdina <phrdina@redhat.com>
This commit is contained in:
Peter Krempa 2022-04-04 16:40:45 +02:00
parent 04deb69bd3
commit b74d418b03
7 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/daemons.rst
View File

@ -100,7 +100,7 @@ optionally, one or two TCP sockets:
with full read-write privileges. A connection to this socket gives the with full read-write privileges. A connection to this socket gives the
client privileges that are equivalent to having a root shell. Access control client privileges that are equivalent to having a root shell. Access control
can be enforced either through validation of `x509 certificates can be enforced either through validation of `x509 certificates
<tlscerts.html>`__, and/or by enabling an `authentication mechanism <kbase/tlscerts.html>`__, and/or by enabling an `authentication mechanism
<auth.html>`__. <auth.html>`__.
NB, some distros will use ``/run`` instead of ``/var/run``. NB, some distros will use ``/run`` instead of ``/var/run``.

3
docs/docs.html.in
View File

@ -28,9 +28,6 @@
<dt><a href="remote.html">Remote access</a></dt> <dt><a href="remote.html">Remote access</a></dt>
<dd>Enable remote access over TCP</dd> <dd>Enable remote access over TCP</dd>
<dt><a href="tlscerts.html">TLS certs</a></dt>
<dd>Generate and deploy x509 certificates for TLS</dd>
<dt><a href="auth.html">Authentication</a></dt> <dt><a href="auth.html">Authentication</a></dt>
<dd>Configure authentication for the libvirt daemon</dd> <dd>Configure authentication for the libvirt daemon</dd>

3
docs/kbase/index.rst
View File

@ -19,6 +19,9 @@ Usage
Examination of the security protections used for QEMU and how they need Examination of the security protections used for QEMU and how they need
configuring to allow use of QEMU passthrough with host files/devices. configuring to allow use of QEMU passthrough with host files/devices.
`TLS certificates <tlscerts.html>`__
Generate and deploy x509 certificates for TLS.
`RPM deployment <rpm-deployment.html>`__ `RPM deployment <rpm-deployment.html>`__
Explanation of the different RPM packages and illustration of which to Explanation of the different RPM packages and illustration of which to
pick for installation pick for installation

1
docs/kbase/meson.build
View File

@ -20,6 +20,7 @@ docs_kbase_files = [
'secureusage', 'secureusage',
'snapshots', 'snapshots',
'systemtap', 'systemtap',
'tlscerts',
'virtiofs', 'virtiofs',
] ]

0
docs/tlscerts.rst → docs/kbase/tlscerts.rst
View File

1
docs/meson.build
View File

@ -109,7 +109,6 @@ docs_rst_files = [
'testapi', 'testapi',
'testsuites', 'testsuites',
'testtck', 'testtck',
'tlscerts',
] ]
# list of web targets to build for docs/web rule # list of web targets to build for docs/web rule

2
docs/remote.html.in
View File

@ -61,7 +61,7 @@ Remote libvirt supports a range of transports:
<dd><a href="https://en.wikipedia.org/wiki/Transport_Layer_Security" title="Transport Layer Security">TLS</a> <dd><a href="https://en.wikipedia.org/wiki/Transport_Layer_Security" title="Transport Layer Security">TLS</a>
1.0 (SSL 3.1) authenticated and encrypted TCP/IP socket, usually 1.0 (SSL 3.1) authenticated and encrypted TCP/IP socket, usually
listening on a public port number. To use this you will need to listening on a public port number. To use this you will need to
<a href="tlscerts.html" title="Generating TLS certificates">generate client and <a href="kbase/tlscerts.html" title="Generating TLS certificates">generate client and
server certificates</a>. server certificates</a>.
The standard port is 16514. The standard port is 16514.
</dd> </dd>