https://bugzilla.novell.com/show_bug.cgi?id=270246 kmachalkova@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED ------- Comment #2 from kmachalkova@novell.com 2007-05-03 03:05 MST ------- Hm, I don't quite understand what this bug has to do with yast2 remote administration module. Yast2 module configures display manager (*dm) in such a way that remote login is possible, enables vnc1 and vnchttpd1 services in xinetd and opens ports 5801 and 5901 in firewall. That's basically it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

https://bugzilla.novell.com/show_bug.cgi?id=270246 max@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |max@novell.com Status|NEEDINFO |ASSIGNED Info Provider|max@novell.com | ------- Comment #4 from max@novell.com 2007-05-03 10:34 MST ------- VNC uses the HTTP port only to deliver the java viewer to the browser. The VNC connection itself is then made from the java viewer to the regular VNC port with the regular VNC protocol, which doesn't support encryption. So, I think it doesn't make much sense to make the mini HTTP server for VNC use HTTPS as long as the VNC connection itself is not encrypted. Encrypted VNC connections are to my knowledge only available in the enterprise edition of RealVNC (closed source, payware) and in the UltraVNC project, which is a fork from the original VNC code and has received changes which make it incompatible with the official VNC protocol. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.