He's essentially looking for the ability to encapsulate packets from another network connection in an RFB message, which doesn't really have anything to do with encryption (I think the only reason ssh was mentioned is because ssh just happens to have the ability to encapsulate network packets in an SSL stream, which from a user's perspective appears to be similar functionality).
The RFB protocol really wasn't designed to do this kind of thing ... RFB is built around framebuffer updates, and it is assumed that very little data other than framebuffer updates will be transfered. That's not to say that you can't use RFB to encapsulate another network connection, but the encapsulated traffic and framebuffer updates will be constantly fighting for the connection, so latency will likely be high for both. However, I agree this would be a useful feature for those times when you don't really care if it is a horribly ugly and inefficient hack as long as it gets the job done (kinda like file transfer via RFB). But I don't know of anyone working on this functionality, so unless you are interested in developing this yourself, I suspect you would have to pay someone to implement this. On Fri, May 28, 2010 at 02:48:07PM -0500, DRC wrote: > On 5/28/10 4:51 AM, Thomas Sondergaard wrote: > > DRC wrote: > >> Why reinvent the wheel? I don't see why it's our job to reproduce the > >> functionality of SSH. Just use SSH. > > > > Convenience is a good answer. Another answer is that VNC is used for > > many things, and not all users that are allowed to access a system with > > VNC is allowed ssh access. > > > > > >> Now, if you instead mean internal encryption of the RFB protocol stream, > >> then didn't we get that as a result of the GNU TLS functionality that > >> Adam added? > > > > Nope, I'm not talking about encryption. > > Why aren't you? What functionality would creating our own SSh tunnel > provide that embedded encryption of the RFB protocol wouldn't provide? > > ------------------------------------------------------------------------------ > > _______________________________________________ > Tigervnc-devel mailing list > Tigervnc-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/tigervnc-devel > ------------------------------------------------------------------------------ _______________________________________________ Tigervnc-devel mailing list Tigervnc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/tigervnc-devel
