Feature #3601
closed
Use secure websockets for console access
Description
As documented in NoVNC under known issues:
when using Firefox, if you use foreman via https, firefox might block the connection (see limiations below), to fix it, goto about:config and enable network.websocket.allowInsecureFromHTTPS
Foreman defaults to https:// only, so every firefox user runs into this. It would also increase security if all console access was encrypted. Websockify does support it, so it's mostly a matter of passing the correct parameters. Ideally the used certificates would be overrideable through settings.yaml.
Updated by Ewoud Kohl van Wijngaarden over 10 years ago
- Status changed from New to Ready For Testing
https://github.com/theforeman/foreman/pull/1024 already tested with VMware and VNC. Needs testing with SPICE.
Updated by Dominic Cleal about 10 years ago
- Has duplicate Feature #4224: Support for TLS Spice connections for console access on libvirt Compute ressources added
Updated by Dominic Cleal almost 10 years ago
- Bugzilla link set to https://bugzilla.redhat.com/show_bug.cgi?id=1107647
Updated by Daniel Lobato Garcia almost 10 years ago
- Has duplicate Feature #1662: Add settings options to secure VNC sessions between Foreman server and client added
Updated by The Foreman Bot almost 10 years ago
- Target version set to 1.8.0
- Pull request https://github.com/theforeman/foreman/pull/1024 added
Updated by Daniel Lobato Garcia almost 10 years ago
- Category changed from Compute resources to Security
- Assignee set to Daniel Lobato Garcia
Updated by Daniel Lobato Garcia almost 10 years ago
- Status changed from Ready For Testing to Closed
Updated by Dominic Cleal almost 10 years ago
- translation missing: en.field_release set to 10
Updated by Ewoud Kohl van Wijngaarden over 9 years ago
https://github.com/theforeman/puppet-foreman/pull/202 enables support by default in the installer.
Updated by Dominic Cleal over 9 years ago
- Related to Bug #7018: SPICE libvirt websockets connections aren't encrypted added