Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Thu, 27 Apr 2000 14:41:22 -0400 Message-Id: <200004271841.OAA03427@envy.delorie.com> From: DJ Delorie To: rdparker AT butlermfg DOT com CC: cygwin-developers AT sourceware DOT cygnus DOT com In-reply-to: <200004271650.MAA14136@delorie.com> (rdparker@butlermfg.com) Subject: Re: [greenbaum AT ti DOT com: cygwin setup and firewalls] References: <200004271650 DOT MAA14136 AT delorie DOT com> > Is there a specific firewall that we are having problems with? I don't know. I don't think users are always smart enough to know more than just "it's a firewall". > I have only run setup.exe from behind a firewall that is why I coded it to > use wininet. That way it would use the same mechanism IE does to go through > the firewall. I did this for somewhat selfish reasons, our #(*&^ proxy at > work ONLY works with IE and wininet compatible software. What about Netscape users? Would they not configure wininet when they configure their Netscape proxy settings? If that's a problem, we can just tell people "hey, you've got to configure IE to work before setup works."