[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [suse-security] Site Firewall/Proxy

To: suse-security@xxxxxxxx
Subject: Re: [suse-security] Site Firewall/Proxy
From: Mathias Homann <admin@xxxxxxxxxx>
Date: Tue, 27 Jul 2004 20:09:19 +0200
Delivered-to: mailing list suse-security@xxxxxxxx
In-reply-to: <200407272002.05976.admin@xxxxxxxxxx>
List-help: <mailto:suse-security-help@suse.com>
List-post: <mailto:suse-security@suse.com>
List-subscribe: <mailto:suse-security-subscribe@suse.com>
List-unsubscribe: <mailto:suse-security-unsubscribe-suse=archive.cert.uni-stuttgart.de@suse.com>
Mailing-list: contact suse-security-help@xxxxxxxx; run by ezmlm
Organization: - private site -
References: <200407271052.32578.neofax_99@xxxxxxxxxxx> <200407272002.05976.admin@xxxxxxxxxx>
Reply-to: admin@xxxxxxxxxx
User-agent: KMail/1.6.2



oh, i forgot a few steps...


after you done all that, install squid (comes with suse) and squidguard on 
said box, configure squid as a transparent proxy (google should help), and 
configure the suse firewall to forward all outgoing traffic to *:80 to thje 
squid port on your firewall instead.
you might want to chain a privoxy banner filter behind that squid (behind as 
seen from the inside of your lan).

bye,
	MH

-- 
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-help@xxxxxxxx
Security-related bug reports go to security@xxxxxxx, not here

References:
- [suse-security] Site Firewall/Proxy
  - From: Terry E. Milnes Jr.
- Re: [suse-security] Site Firewall/Proxy
  - From: Mathias Homann

Prev by Date: Re: [suse-security] Site Firewall/Proxy
Next by Date: Re: [suse-security] Site Firewall/Proxy
Previous by thread: Re: [suse-security] Site Firewall/Proxy
Next by thread: Re: [suse-security] Site Firewall/Proxy
Index(es):
- Date
- Thread