|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: [NTSEC] By-passing MS Proxy 2.0 and others packet filtering
Kevin Way (kevin
RESEARCH-INC.COM)Wed, 14 Oct 1998 13:46:00 -0400
- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: klindsay: "Secure Locate v1.2"
- Previous message: Allen Myers - Verio Consulting Group: "Re: Annoying Solaris/CDE/NIS+ bug"
- In reply to: Peter van Dijk: "Re: [NTSEC] By-passing MS Proxy 2.0 and others packet filtering"
> Very untrue. Look at this: > [hardbeathaarlem hardbeat]$ telnet proxy 8080 > Trying 194.178.232.18... > Connected to rotterdam.vuurwerk.nl. > Escape character is '^]'. > POST http://telnet:23/ HTTP/1.0 > this seems to me to just be a poorly configured proxy server. the following acl's take care of that problem nicely, on squid anyway. acl SSL_ports port 443 563 acl Safe_ports port 80 21 70 1025-5999 6011-65535 acl CONNECT method CONNECT http_access deny CONNECT !SSL_ports http_access deny !Safe_ports this would seem to me a simple, and proper way to stop that problem nicely with squid. Kevin Way System Administrator ReSearch Inc.
- Next message: klindsay: "Secure Locate v1.2"
- Previous message: Allen Myers - Verio Consulting Group: "Re: Annoying Solaris/CDE/NIS+ bug"
- In reply to: Peter van Dijk: "Re: [NTSEC] By-passing MS Proxy 2.0 and others packet filtering"