with full read-write privileges. A connection to this socket gives the
client privileges that are equivalent to having a root shell. Access control
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>`__.
NB, some distros will use ``/run`` instead of ``/var/run``.
<dt><a href="remote.html">Remote access</a></dt>
<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>
<dd>Configure authentication for the libvirt daemon</dd>
Examination of the security protections used for QEMU and how they need
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>`__
Explanation of the different RPM packages and illustration of which to
pick for installation
'secureusage',
'snapshots',
'systemtap',
+ 'tlscerts',
'virtiofs',
]
'testapi',
'testsuites',
'testtck',
- 'tlscerts',
]
# list of web targets to build for docs/web rule
<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
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>.
The standard port is 16514.
</dd>