Bug 1449307

Summary: [RFE][nova]: Generic Framework for Securing VNC and SPICE Proxy-To-Compute-Node Connections
Product: Red Hat OpenStack Reporter: Paul Needle <pneedle>
Component: openstack-novaAssignee: Eoghan Glynn <eglynn>
Status: CLOSED DUPLICATE QA Contact: Prasanth Anbalagan <panbalag>
Severity: low Docs Contact:
Priority: high    
Version: 10.0 (Newton)CC: berrange, dasmith, eglynn, kchamart, markmc, panbalag, rhos-integ, sbauza, sclewis, sferdjao, sgordon, srevivo, stephenfin, vromanso, yeylon
Target Milestone: ---Keywords: FutureFeature, ZStream
Target Release: 10.0 (Newton)   
Hardware: All   
OS: Linux   
URL: https://blueprints.launchpad.net/nova/+spec/websocket-proxy-to-host-security
Whiteboard: upstream_milestone_none upstream_definition_approved upstream_status_needs-code-review
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1086964 Environment:
Last Closed: 2017-10-06 13:54:43 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Paul Needle 2017-05-09 14:55:58 UTC 
+++ This bug was initially created as a clone of Bug #1086964, so that the feature could be considered for back-port to OSP 10 +++

Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/websocket-proxy-to-host-security.

Description:

Currently, while the noVNC and HTML5 SPICE clients can use TLS-encrypted
WebSockets to communicate with Websockify (and authenticate with Nova console
tokens), the encryption and authentication ends there.  There are neither
encryption nor authentication between Websockify and the hypervisors'
VNC and SPICE servers.

This blueprint would propose introducing a generic framework for supporting
MITM security for Websockify to use between itself and the compute nodes.


Specification URL (additional information):

None
Comment 3 Stephen Finucane 2017-10-06 13:54:43 UTC 

*** This bug has been marked as a duplicate of bug 1025429 ***