Project

General

Profile

Actions

Feature #1662

closed

Add settings options to secure VNC sessions between Foreman server and client

Added by Anonymous almost 12 years ago. Updated almost 10 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Right now, in order to enable SSL for noVNC between the foreman server and client, it is necessary to update /usr/share/foreman/lib/vnc_proxy.rb install and every update from:
cmd = "#{ws_proxy} --daemon --run-once --timeout=#{timeout} #{port} #{host}:#{host_port}"
to:
cmd = "#{ws_proxy} --daemon --run-once --timeout=#{timeout} #{port} #{host}:#{host_port} --cert=<file-containing-cert-and-key> --ssl-only"

And I believe it is also necessary to edit /var/lib/foreman/public/javascripts/noVNC/rfb.js and change:
if (conf.encrypt) {
uri = "wss://";
} else {
uri = "ws://";
}
to:
if (conf.encrypt) {
uri = "wss://";
} else {
uri = "wss://";
}
though this looks like it should work without modification as expected if conf.encrypt gets set true where ever necessary.

My thinking is that maybe this can be configured from the settings within the webui by setting the cert file in a similar fashio to the ssl_certificate option, and have a secure vnc true/false option similar to the others available, that will then set things up to run accordingly.


Related issues 1 (0 open1 closed)

Is duplicate of Foreman - Feature #3601: Use secure websockets for console accessClosedDaniel Lobato Garcia11/07/2013Actions
Actions

Also available in: Atom PDF