Security Basics mailing list archives
Re: Restricting Open Proxies
From: "Jay" <jay.tomas () infosecguru com>
Date: Fri, 22 Jun 2007 13:53:04 -0400
I think there is some confusion. Either on my part or some of the other posters. The issue is not they are getting out of the network through an open proxy, at least I hope not, because if thats the case then they have bigger problems with network config. The issue is that once they go out their proxy they hit another one to obfuscate where they are coming from. However, by going thorugh the open proxy they danger themselves up to information leakage/interception which was the original concern. Perhaps the original poster can clarify? Jay ----- Original Message ----- From: merigoth () gmail com [mailto:merigoth () gmail com] To: security-basics () securityfocus com Sent: 21 Jun 2007 23:50:03 -0000 Subject: Re: Restricting Open Proxies I haven't looked too deeply into this. If the corporate is using windows 2k/xp, you could consider setting the GPO to restrict modification of the INNET settings. (technet.microsoft.com/en-us/library/bb457144.aspx). Of course, this still doesn't stop cgi/web-based proxies.
Current thread:
- Restricting Open Proxies shailesh . rangari (Jun 19)
- Re: Restricting Open Proxies Samir Pawaskar (Jun 21)
- Open Source Router with NAT Mohamed Farid (Jun 28)
- Re: Open Source Router with NAT Dathan Bennett (Jun 30)
- Re: Open Source Router with NAT Nikhil Wagholikar (Jun 30)
- Open Source Router with NAT Mohamed Farid (Jun 28)
- <Possible follow-ups>
- Re: Restricting Open Proxies krymson (Jun 19)
- Re: Restricting Open Proxies Jay (Jun 22)
- Re: Restricting Open Proxies merigoth (Jun 22)
- Re: Restricting Open Proxies Jay (Jun 22)
- Re: Restricting Open Proxies Samir Pawaskar (Jun 21)