> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > > ----- Original Message ----- > From: "Beerse, Corni" <[EMAIL PROTECTED]> > To: "'Dominik Stok?osa'" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>; > <[EMAIL PROTECTED]> > Sent: Tuesday, July 29, 2003 4:29 AM > Subject: RE: VNC and SSL > [snip] > > If you need to use ssl, then security is required. > > If security is required, then you should not use the java > viewer. Having > > the java viewer active is kind of like having the ladder > out at night. Its > > like giving the hackers the tool they need. > > > > If you need access over a public network, use the binary > viewer for your > > desktop. > > Why again is the JavaViewer more insecure than the native > client? After all, > it's just a jar file that connects to the same exact port as > the native > client. Perhaps having the webserver would be a risk, but you > could have > apache serve the applets (as long as it appears to be on the > same machine).
The java viewer on its own is just as secure as all other viewers. It is the way the java viewer is (can be) distributed from the vncserver that makes the entire package insecure. With respect to my prevouis messages, I do have to add that I most times refer to the java viewer as the one at port 5800 of the vncserver (or an other webwerver on the same machine). The java-viewer that is started from the desktop machine is just as save as the binary viewer. CBee _______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
