RE: HTTPS, proxies, and remote developers.

["Eugene Kuznetsov" <eugene () datapower com>]

> me. The remote client does not like the idea.
> 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).

Why not an outbound SSL proxy, where the developers open up an SSL
session to the proxy, everything can be scanned in clear-text on the
proxy, and then the proxy re-initiates an SSL connection to the
mothership? This would also mean that only authorized staff on client
site would be able to see the traffic, not everyone. 

_______________________________________________
firewall-wizards mailing list
firewall-wizards () honor icsalabs com
http://honor.icsalabs.com/mailman/listinfo/firewall-wizards