NuKVM/libvirt
3
0
Fork 0
mirror of https://github.com/libvirt/libvirt.git synced 2025-02-25 18:55:26 -06:00
Code Issues Packages Projects Releases Wiki Activity

docs/auth.html.in: fixed typos

Browse Source 
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
Signed-off-by: Andrew Miloradovsky <andrew@interpretmath.pw>
This commit is contained in:
Andrew Miloradovsky 2019-12-19 18:01:28 +03:00 committed by Daniel P. Berrangé
parent dfff16a7c2
commit efeb9d710d
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/auth.html.in
View File

@ -274,7 +274,7 @@ to turn on SASL auth in these listeners.
</p> </p>
<p> <p>
Since the libvirt SASL config file defaults to using GSSAPI (Kerberos), a Since the libvirt SASL config file defaults to using GSSAPI (Kerberos), a
config change is rquired to enable plain password auth. This is done by config change is required to enable plain password auth. This is done by
editting <code>/etc/sasl2/libvirt.conf</code> to set the <code>mech_list</code> editting <code>/etc/sasl2/libvirt.conf</code> to set the <code>mech_list</code>
parameter to <code>scram-sha-1</code>. parameter to <code>scram-sha-1</code>.
</p> </p>
@ -317,7 +317,7 @@ in these scenarios - only the plain TCP listener needs encryption
Some operating systems do not install the SASL kerberos plugin by default. It Some operating systems do not install the SASL kerberos plugin by default. It
may be necessary to install a sub-package such as <code>cyrus-sasl-gssapi</code>. may be necessary to install a sub-package such as <code>cyrus-sasl-gssapi</code>.
To check whether the Kerberos plugin is installed run the <code>pluginviewer</code> To check whether the Kerberos plugin is installed run the <code>pluginviewer</code>
program and verify that <code>gssapi</code> is listed,eg: program and verify that <code>gssapi</code> is listed, e.g.:
</p> </p>
<pre> <pre>
# pluginviewer # pluginviewer
@ -359,7 +359,7 @@ kadmin.local: quit
<p> <p>
Any client application wishing to connect to a Kerberos enabled libvirt server Any client application wishing to connect to a Kerberos enabled libvirt server
merely needs to run <code>kinit</code> to gain a user principal. This may well merely needs to run <code>kinit</code> to gain a user principal. This may well
be done automatically when a user logs into a desktop session, if PAM is setup be done automatically when a user logs into a desktop session, if PAM is set up
to authenticate against Kerberos. to authenticate against Kerberos.
</p> </p>
</body> </body>