[Zebedee-talk] FW: [Ultravnc-list] Re: "Add New Client" through PROXY servers on port 443 or 80?

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

I notice that Zebedee has an existing HTTP proxy feature which would =
seem to
be ideal for the application Graeme and Joel are describing, if it could =
be
made to work with proxies requiring authentication.

At least as of the current stable version (2.4.1), Zebedee does not seem =
to
work on an ISA http proxy which is configured to require authentication.
Would there be any interest in working with Graeme and others in the VNC
community to add authentication to the capabilities of the HTTP proxy
feature of Zebedee?  The same techniques should apply equally well to an
effort to provide built-in proxy support for UltraVNC.

- w.h.

-----Original Message-----
From: ult...@li...
[mailto:ult...@li...] On Behalf Of =
Hazelrig,
William
Sent: Tuesday, December 30, 2003 8:48 AM
To: ult...@li...; Joel Bomgaars
Cc: in...@ex...; vnc...@re...; tig...@ti...
Subject: RE: [Ultravnc-list] Re: "Add New Client" through PROXY servers =
on
port 443 or 80?

Aren't the Windows "internet settings", containing current proxy
information for the default browser, stored in one location or at most a
small set of possibly locations in the registry?  WinVNC and UltraVNC
alike incorporate code to read data from the ORL branch; it should be
possible to use that same code to read the proxy settings from the
Windows internet settings branch if its location(s) under each O/S can
be identified.

- w.h.

-----Original Message-----
From: Graeme Pyle [mailto:gr...@Gr...]=20
Sent: Tuesday, December 30, 2003 5:03 AM
To: Joel Bomgaars
Cc: in...@ex...; ult...@li...;
vnc...@re...; tig...@ti...
Subject: [Ultravnc-list] Re: "Add New Client" through PROXY servers on
port 443 or 80?

Hi Joel,

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,=20
"auto-detect" and "configuration URL" stuff is more difficult. Will=20
require linking against WinHTTP (which I think isn't support in 95+98).=20
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 is=20
always 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 SSL

respectively.

This is more tricky, and may involve modifying the client too. More=20
investigation needed.

 > 6. The proxy server compatibility must be active when using the=20
"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,=20
> (Ultr@VNC <mailto:Ultr@VNC> Developers)
>=20
> "Add New Client" proxy server compatibility is the next major=20
> enhancement we would like to sponsor with Ultr@VNC. <mailto:Ultr@VNC>=20
> The email below is from Graeme of the RealVNC mailing list, and it
looks=20
> like the source for his patched version of winvnc.exe may be a great=20
> head start (http://www.graemepyle.com/VNC).=20
> <http://www.graemepyle.com/VNC> Here are the requirements:
>=20
> 1. The "Add New Client" must dynamically detect the proxy server=20
> (possibly by reading the Internet Explorer properties).
> 2. It must forward traffic to the proxy server in a format that the=20
> proxy server understands.
> 3. It must be able to use port 80 or 443 or another port that is
always=20
> open.
> 4. The download size must remain reasonable for winvnc.exe +=20
> vnchooks.dll (currently ~ 336KB)
> 5. If possible, port 80 or 443 traffic must masquerade as HTTP or SSL=20
> (respectively)
> 6. The proxy server compatibility must be active when using the
"winvnc=20
> -connect" from the command line.
>=20
> Graeme: Could your source code be altered to fit the above
requirements?=20
> Would you be interested in having your GNU GPL developments sponsored?
> Sam and Rudi: How difficult would it be to incorporate Graeme's work=20
> into Ultr@VNC? Is there other source code available that would benefit

> this endeavor?
> Eric: Scott Weaver mentioned that you had done some work with
tunneling=20
> VNC traffic and making it proxy server compatible. Do you have any=20
> thoughts or insights into this? Have you written any code that we
could=20
> purchase that would help this project? Would you like to be involved
in=20
> sponsored GNU GPL developments?
>=20
> 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=20
> the GPL as part of Ultr@VNC. <mailto:Ultr@VNC> Sponsorship is
available=20
> to make the developments worth your time and effort. I hope that this=20
> will be a great win/win endeavor that benefits everyone.
>=20
> Please let me know if any of you are interested or have any feedback
or=20
> 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
>=20
>=20
>  > Hi Joel,
>=20
> 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%.
>=20
> 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.
>=20
> 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.
>=20
> http://www.graemepyle.com/VNC
>=20
> Cheers,
> Graeme
>=20

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys
admin.
Click now! http://ads.osdn.com/?ad_id=3D1278&alloc_id=3D3371&op=3Dclick

Confidentiality Notice:
The information contained in this email message is privileged and
confidential information and intended only for the use of the individual =
or
entity named in the address.  If you are not the intended recipient, you =
are
hereby notified that any dissemination, distribution, or copying of this
information is strictly prohibited.  If you received this information in
error, please notify the sender and delete this information from your
computer and retain no copies of any of this information.

-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for =
IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys =
admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id371&op=3Dick