Firewall Wizards mailing list archives
RE: HTTPS, proxies, and remote developers.
From: "Melson, Paul" <PMelson () sequoianet com>
Date: Mon, 16 Jun 2003 08:36:51 -0400
Take the connections off a public network. It may be time to explore a T1, ISDN, dial-up, or other "private" connection. Then that connection should be filtered similarly to what you allow across the Internet. PaulM
-----Original Message----- What would be the easiest way to handle this situation? How would you resolve a policy issue if one of your clients requires that you use unencrypted traffic outbound from their network into yours. (Their need to know for traffic on their network against your need for security).
_______________________________________________ firewall-wizards mailing list firewall-wizards () honor icsalabs com http://honor.icsalabs.com/mailman/listinfo/firewall-wizards
Current thread:
- HTTPS, proxies, and remote developers. Devdas Bhagat (Jun 15)
- Re: HTTPS, proxies, and remote developers. Barney Wolff (Jun 15)
- Re: HTTPS, proxies, and remote developers. Paul Robertson (Jun 15)
- RE: HTTPS, proxies, and remote developers. Eugene Kuznetsov (Jun 16)
- <Possible follow-ups>
- Re: HTTPS, proxies, and remote developers. simonis (Jun 15)
- RE: HTTPS, proxies, and remote developers. Melson, Paul (Jun 16)
- RE: HTTPS, proxies, and remote developers. Hilal Hussein (Jun 22)