From: Sergii Zasenko <ser...@zasenko.name> - Remove unix socket option limitation for VNC websocket - Reflect websocket option changes in documentation
Signed-off-by: Sergii Zasenko <ser...@zasenko.name> Reviewed-by: Marc-André Lureau <marcandre.lur...@redhat.com> Message-Id: <20230724100353.16628-1-ser...@zasenko.name> --- ui/vnc.c | 5 ----- qemu-options.hx | 4 ++++ 2 files changed, 4 insertions(+), 5 deletions(-) diff --git a/ui/vnc.c b/ui/vnc.c index b3fd78022b..dd530f04e5 100644 --- a/ui/vnc.c +++ b/ui/vnc.c @@ -3734,11 +3734,6 @@ static int vnc_display_get_address(const char *addrstr, addr->type = SOCKET_ADDRESS_TYPE_UNIX; addr->u.q_unix.path = g_strdup(addrstr + 5); - if (websocket) { - error_setg(errp, "UNIX sockets not supported with websock"); - goto cleanup; - } - if (to) { error_setg(errp, "Port range not support with UNIX socket"); goto cleanup; diff --git a/qemu-options.hx b/qemu-options.hx index f5c01eeeb4..4d19660336 100644 --- a/qemu-options.hx +++ b/qemu-options.hx @@ -2516,6 +2516,10 @@ SRST host. It is possible to control the websocket listen address independently, using the syntax ``websocket``\ =host:port. + Websocket could be allowed over UNIX domain socket, using the syntax + ``websocket``\ =unix:path, where path is the location of a unix socket + to listen for connections on. + If no TLS credentials are provided, the websocket connection runs in unencrypted mode. If TLS credentials are provided, the websocket connection requires encrypted client connections. -- 2.41.0.28.gd7d8841f67