Yip, I would certainly be interested in having the proxy work sponsored.
With regards to the requirements:
1. The "Add New Client" must dynamically detect the proxy server (possibly by reading the Internet Explorer properties).
Have done for manually given IE proxy settings, no problem. However, "auto-detect" and "configuration URL" stuff is more difficult. Will require linking against WinHTTP (which I think isn't support in 95+98). Need to investigate further.
2. It must forward traffic to the proxy server in a format that the proxy server understands.
Done. No problem.
3. It must be able to use port 80 or 443 or another port that isalways open.
Done.
4. The download size must remain reasonable for winvnc.exe + vnchooks.dll (currently ~ 336KB)
Done.
5. If possible, port 80 or 443 traffic must masquerade as HTTP or SSLrespectively.
This is more tricky, and may involve modifying the client too. More investigation needed.
6. The proxy server compatibility must be active when using the"winvnc -connect" from the command line.
Easily done
I'm sure we could build-on from what I have so far. Let me know what you think.
Cheers, Graeme
Joel Bomgaars wrote:
Dear Eric (E-bay Developer), Graeme (VNC-proxy Developer), Sam and Rudi, ([EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Developers)
"Add New Client" proxy server compatibility is the next major enhancement we would like to sponsor with [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> The email below is from Graeme of the RealVNC mailing list, and it looks like the source for his patched version of winvnc.exe may be a great head start (http://www.graemepyle.com/VNC). <http://www.graemepyle.com/VNC> Here are the requirements:
1. The "Add New Client" must dynamically detect the proxy server (possibly by reading the Internet Explorer properties).
2. It must forward traffic to the proxy server in a format that the proxy server understands.
3. It must be able to use port 80 or 443 or another port that is always open.
4. The download size must remain reasonable for winvnc.exe + vnchooks.dll (currently ~ 336KB)
5. If possible, port 80 or 443 traffic must masquerade as HTTP or SSL (respectively)
6. The proxy server compatibility must be active when using the "winvnc -connect" from the command line.
Graeme: Could your source code be altered to fit the above requirements? Would you be interested in having your GNU GPL developments sponsored?
Sam and Rudi: How difficult would it be to incorporate Graeme's work into [EMAIL PROTECTED] Is there other source code available that would benefit this endeavor?
Eric: Scott Weaver mentioned that you had done some work with tunneling VNC traffic and making it proxy server compatible. Do you have any thoughts or insights into this? Have you written any code that we could purchase that would help this project? Would you like to be involved in sponsored GNU GPL developments?
If any other VNC developers would like to be involved in this project, the outcome would benefit the entire VNC community and be released under the GPL as part of [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> Sponsorship is available to make the developments worth your time and effort. I hope that this will be a great win/win endeavor that benefits everyone.
Please let me know if any of you are interested or have any feedback or input. I hope to hear from you soon.
Thanks,
Joel Bomgaars
MCSE, CNE, ASE, CCNA, CCDA, A+, Network+, Server+, i-Net+, CIW, MOUS
Senior System Engineer and Software Developer
www.expertvnc.com <http://www.expertvnc.com>
(601) 914-2444
> Hi Joel,
Yes, that would work. I've written a small Java proxy app that connects to the local VNC server and then back to our office through a Microsoft ISA server ("CONNECT mybox:443 HTTP/1.1") and it works 100%.
If there was a firewall that did content-inspection, it might notice that you weren't talking SSL and stop the connection. But I think those would be far and few between.
I'm trying to change that VNC "Add New Client" dialog to support Proxy settings, but my C/C++/Windows is rusty. I've just gotten hold of Visual Studio 6, so I'm hoping I'll be able to make that work soon - will let you know.
http://www.graemepyle.com/VNC
Cheers, Graeme
_______________________________________________ VNC-List mailing list [EMAIL PROTECTED] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
