Fri Feb 14 17:32:01 2003
On Fri, 14 Feb 2003, "Beerse, Corni" wrote:
> I think the simple answer is: vnc cannot because it cannot code itself.
> The developpers willnot/cannot because it is not in the developmentpath.
> As far as I'm concerned, the developmentpath for the core vnc
> development will not incorporate new features like these as long as the
> spinoffs like zvnc, yvnc, xvnc, wvnc, vvnc, uvnc and such have not
> implemented it successfully and satisfactory.
Do those spinoffs really exist? They are trying to implement SSH within
VNC and they have all failed? If so, that is very interesting and
I hope the realVNC development team will consider this as a worthwhile
project for someday.
> > -----Original Message-----
> > From: Mike Miller [mailto:email@example.com]
> > Sent: vrijdag 14 februari 2003 16:23
> > To: firstname.lastname@example.org
> > Cc: VNC-List@realvnc.com
> > Subject: Re: Automatic Encryption
> > Here's a simple question: Why can't VNC server and viewer just use
> > established SSH protocols to communicate? Incorporate OpenSSH code
> > into the server and PuTTY (or whatever) code into the viewer. Isn't
> > that workable? The keys wouldn't be encoded in the password, they
> > would be handled in the way that SSH normally handles them.
> > Mike