"README.rst" did not exist on "ea99dde191379804cb01881f931cd50db6550df7"
-
Daniel P. Berrangé authored
When TLS is required, the primary VNC server considers it to be mandatory. ie the server admin decides whether or not TLS is used, and the client has to comply with this decision. The websockets server, however, treated it as optional, allowing non-TLS clients to connect to a server which had setup TLS. Thus enabling websockets lowers the security of the VNC server leaving the admin no way to enforce use of TLS. This removes the code that allows non-TLS fallback in the websockets server, so that if TLS is requested for VNC it is now mandatory for both the primary VNC server and the websockets VNC server. Signed-off-by:
Daniel P. Berrange <berrange@redhat.com> Signed-off-by:
Gerd Hoffmann <kraxel@redhat.com>
Daniel P. Berrangé authoredWhen TLS is required, the primary VNC server considers it to be mandatory. ie the server admin decides whether or not TLS is used, and the client has to comply with this decision. The websockets server, however, treated it as optional, allowing non-TLS clients to connect to a server which had setup TLS. Thus enabling websockets lowers the security of the VNC server leaving the admin no way to enforce use of TLS. This removes the code that allows non-TLS fallback in the websockets server, so that if TLS is requested for VNC it is now mandatory for both the primary VNC server and the websockets VNC server. Signed-off-by:
Daniel P. Berrange <berrange@redhat.com> Signed-off-by:
Gerd Hoffmann <kraxel@redhat.com>