diff options
| author | Tim Hardeck <thardeck@suse.de> | 2013-04-23 16:33:01 +0200 |
|---|---|---|
| committer | Anthony Liguori <aliguori@us.ibm.com> | 2013-05-03 12:04:57 -0500 |
| commit | 0057a0d59006d00c294de0b012d9a290eb1a5c80 (patch) | |
| tree | 5eb08a6086fe37394127fb6eb97b9141025061a6 /ui/vnc-ws.h | |
| parent | 8f3b664f6cc4153cc73941c941d54c4e499b7537 (diff) | |
| download | qemu-0057a0d59006d00c294de0b012d9a290eb1a5c80.tar.gz | |
TLS support for VNC Websockets
Added TLS support to the VNC QEMU Websockets implementation.
VNC-TLS needs to be enabled for this feature to be used.
The required certificates are specified as in case of VNC-TLS
with the VNC parameter "x509=<path>".
If the server certificate isn't signed by a rooth authority it needs to
be manually imported in the browser because at least in case of Firefox
and Chrome there is no user dialog, the connection just gets canceled.
As a side note VEncrypt over Websocket doesn't work atm because TLS can't
be stacked in the current implementation. (It also didn't work before)
Nevertheless to my knowledge there is no HTML 5 VNC client which supports
it and the Websocket connection can be encrypted with regular TLS now so
it should be fine for most use cases.
Signed-off-by: Tim Hardeck <thardeck@suse.de>
Reviewed-by: Anthony Liguori <aliguori@us.ibm.com>
Message-id: 1366727581-5772-1-git-send-email-thardeck@suse.de
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'ui/vnc-ws.h')
| -rw-r--r-- | ui/vnc-ws.h | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/ui/vnc-ws.h b/ui/vnc-ws.h index 039a58765c..95c1b0aeae 100644 --- a/ui/vnc-ws.h +++ b/ui/vnc-ws.h @@ -74,6 +74,9 @@ enum { WS_OPCODE_PONG = 0xA }; +#ifdef CONFIG_VNC_TLS +void vncws_tls_handshake_peek(void *opaque); +#endif /* CONFIG_VNC_TLS */ void vncws_handshake_read(void *opaque); long vnc_client_write_ws(VncState *vs); long vnc_client_read_ws(VncState *vs); |