|
Bugzilla – Full Text Bug Listing |
| Summary: | Remote administration should run as https | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE 10.3 | Reporter: | Forgotten User 7L3tOtZIov <forgotten_7L3tOtZIov> |
| Component: | YaST2 | Assignee: | Katarina Machalkova <kmachalkova> |
| Status: | RESOLVED WONTFIX | QA Contact: | Jiri Srain <jsrain> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | CC: | max |
| Version: | Alpha 3 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | openSUSE 10.3 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User 7L3tOtZIov
2007-05-01 11:07:35 UTC
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. How does the configuration change if https is to be used? Does tightvnc (which yast installs by default) support it? Reinhard, can you comment? 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. Wontfix then |