diff options
author | Daniel P. Berrange <berrange@redhat.com> | 2015-03-17 13:42:55 +0000 |
---|---|---|
committer | Gerd Hoffmann <kraxel@redhat.com> | 2015-03-18 09:25:13 +0100 |
commit | d169f04b8b8424ad9c5377bb5391de2f760e3db1 (patch) | |
tree | d611076f8cdd1e53d5eaa3ab03834f047a01bacf /ui/vnc.h | |
parent | 153130cd4fa236e29bb6243eebf9439b983ca266 (diff) | |
download | hqemu-d169f04b8b8424ad9c5377bb5391de2f760e3db1.zip hqemu-d169f04b8b8424ad9c5377bb5391de2f760e3db1.tar.gz |
ui: report error if user requests VNC option that is unsupported
If the VNC server is built without tls, sasl or websocket support
and the user requests one of these features, they are just silently
ignored. This is bad because it means the VNC server ends up running
in a configuration that is less secure than the user asked for.
It also leads to an tangled mass of preprocessor conditionals when
configuring the VNC server.
This ensures that the tls, sasl & websocket options are always
processed and an error is reported back to the user if any of
them were disabled at build time.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
Diffstat (limited to 'ui/vnc.h')
-rw-r--r-- | ui/vnc.h | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -180,10 +180,10 @@ struct VncDisplay char *password; time_t expires; int auth; + int subauth; /* Used by VeNCrypt */ bool lossy; bool non_adaptive; #ifdef CONFIG_VNC_TLS - int subauth; /* Used by VeNCrypt */ VncDisplayTLS tls; #endif #ifdef CONFIG_VNC_SASL @@ -284,9 +284,9 @@ struct VncState int minor; int auth; + int subauth; /* Used by VeNCrypt */ char challenge[VNC_AUTH_CHALLENGE_SIZE]; #ifdef CONFIG_VNC_TLS - int subauth; /* Used by VeNCrypt */ VncStateTLS tls; #endif #ifdef CONFIG_VNC_SASL |