Actions
Bug #7018
open
SPICE libvirt websockets connections aren't encrypted
Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - libvirt
Target version:
-
Description
When setting up a libvirt VM, the websockets connection isn't encrypted when the websockets_ssl* settings are appropriately configured, but VNC ones are.
Updated by Dominic Cleal over 9 years ago
- Related to Feature #3601: Use secure websockets for console access added
Updated by Dominic Cleal over 9 years ago
- Category changed from Compute resources to Compute resources - libvirt
Updated by Dominic Cleal over 9 years ago
- Related to Feature #7805: Add several security related HTTP headers - security hardening. added
Updated by Dominic Cleal over 9 years ago
This is causing a problem now with Chrome since #7805, as it's not permitting mixed content by default.
https://github.com/theforeman/foreman/pull/1882#issuecomment-61255793
To workaround, click the shield in the address bar, then "Load unsafe script".
Updated by Anonymous over 7 years ago
- Related to Feature #2569: [RFE] Add ability to encrypt HTML5 spice client added
Updated by Oliver Freyermuth almost 6 years ago
- Triaged set to No
Seems that for Firefox, network.websocket.allowInsecureFromHTTPS is needed in about:config.
Things still fail for me then, but also VNC failed - still investigating.
Actions