On Tuesday 21 February 2006 03:17, Pablo J Royo wrote: > Hello Hal: > > Take a look to: > > http://spipe.sourceforge.net/concrete_example2.html > > I must admit it is not a usual solution , but it could be an option if your > web server is an 1.3.X Apache one and you have control over it. > What it does is to cipher with SSL all outgoing traffic at client, and to > decipher it at the end web server, forwarding to the final VNC server. > Also, the end Web server keeps on serving HTTP requests, so with your 443 > port you can serve both VNC and HTTP at the same time.
When I first saw this, I thought, "No way!", since I don't want to add any more middleware than I need. But it has a link to stunnel, which I'm examining now and that may prove to be exactly what I need. That would be a huge relief, since I spent most of yesterday and last night looking into sockets and SSL in Java. I reached the conclusion it can be done in Java, and probably fairly easily (at least easy in relation to anything in Java -- a simple Perl script of 15 lines takes literally 150-200 lines in Java). I'd just have to learn a lot before I can do it. If stunnel works, it'd save me several days of work! So thanks for what could save me a lot of work. I'll post if it works and, if it does, I'll post enough info on how to do it so others can set it up. Hal _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
