Hi Hamish, Hmm, this doesn't sound right since SSL doesn't use port 80 but 443 as you point out. Sounds like either the s/ware is bad or there is a configuration problem.You could try using the Firewall Tool Kit at www.ftwk.org which is an application level set of proxies. However, I would ask the software people more about how it is trying to connect as it looks like you should be able to get straight to the destination.
Good luck, Steve On Wed, Aug 18, 1999 at 09:20:56PM +1000, Hamish Moffatt wrote: > Some application software we have here (running on a Microsoft OS, even) > needs to open an SSL connection to a remote server. It supports tunneling > through proxy servers, but only proxy servers which require authentication. > Our ISP's proxy does not require authentication, and the software > can't handle it. (This is the most outrageous thing I've ever heard, > but that's the way it is.) > > I want to set up some piece of software locally which will accept > the authenticated connection and pass this on to the ISP's proxy. > What software do I need to do this? I have no idea how these tunnels work. > > > (General discussion: our ISP blocks outbound connects on port 80 so > as to enforce proxy usage. All other ports are transparent. It would > seem that the software is trying to talk to a remote web server. However, > as far as I understand it, SSL http connections are usually done on > port 443, which isn't blocked by our ISP. Thoughts?) > > > Hamish > -- > Hamish Moffatt VK3SB (ex-VK3TYD). > CCs of replies from mailing lists are welcome. > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
