blob: fb8a92ba587e081eec35a141eb6b284216c2a35c [file] [log] [blame]
Daniel P. Berrangec6a9a9f2017-03-15 11:53:22 +00001# If you want to use VNC remotely without TLS, then you *must*
2# pick a mechanism which provides session encryption as well
3# as authentication.
aliguori2f9606b2009-03-06 20:27:28 +00004#
Daniel P. Berrangec6a9a9f2017-03-15 11:53:22 +00005# If you are only using TLS, then you can turn on any mechanisms
aliguori2f9606b2009-03-06 20:27:28 +00006# you like for authentication, because TLS provides the encryption
7#
Daniel P. Berrangec6a9a9f2017-03-15 11:53:22 +00008# If you are only using UNIX sockets then encryption is not
9# required at all.
aliguori2f9606b2009-03-06 20:27:28 +000010#
Daniel P. Berrangec6a9a9f2017-03-15 11:53:22 +000011# NB, previously DIGEST-MD5 was set as the default mechanism for
12# QEMU VNC. Per RFC 6331 this is vulnerable to many serious security
13# flaws as should no longer be used. Thus GSSAPI is now the default.
14#
15# To use GSSAPI requires that a QEMU service principal is
16# added to the Kerberos server for each host running QEMU.
17# This principal needs to be exported to the keytab file listed below
18mech_list: gssapi
19
20# If using TLS with VNC, or a UNIX socket only, it is possible to
21# enable plugins which don't provide session encryption. The
22# 'scram-sha-1' plugin allows plain username/password authentication
23# to be performed
24#
25#mech_list: scram-sha-1
26
27# You can also list many mechanisms at once, and the VNC server will
28# negotiate which to use by considering the list enabled on the VNC
29# client.
30#mech_list: scram-sha-1 gssapi
aliguori2f9606b2009-03-06 20:27:28 +000031
32# Some older builds of MIT kerberos on Linux ignore this option &
33# instead need KRB5_KTNAME env var.
34# For modern Linux, and other OS, this should be sufficient
Laszlo Ersekdfb38042014-03-14 15:39:36 +010035#
Daniel P. Berrangec6a9a9f2017-03-15 11:53:22 +000036# This file needs to be populated with the service principal that
37# was created on the Kerberos v5 server. If switching to a non-gssapi
38# mechanism this can be commented out.
39keytab: /etc/qemu/krb5.tab
aliguori2f9606b2009-03-06 20:27:28 +000040
Daniel P. Berrangec6a9a9f2017-03-15 11:53:22 +000041# If using scram-sha-1 for username/passwds, then this is the file
aliguori2f9606b2009-03-06 20:27:28 +000042# containing the passwds. Use 'saslpasswd2 -a qemu [username]'
Cole Robinson805695d2013-07-09 10:07:53 -040043# to add entries, and 'sasldblistusers2 -f [sasldb_path]' to browse it
Daniel P. Berrangec6a9a9f2017-03-15 11:53:22 +000044#sasldb_path: /etc/qemu/passwd.db