From owner-freebsd-questions@FreeBSD.ORG Thu Jan 20 11:07:33 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B5F9416A4CE for ; Thu, 20 Jan 2005 11:07:33 +0000 (GMT) Received: from hobbes.brasapen.org (tafkam.xs4all.nl [82.92.76.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7C1743D2F for ; Thu, 20 Jan 2005 11:07:30 +0000 (GMT) (envelope-from tafkam@brasapen.org) Received: from webmail.home.brasapen.org (www.bos-zuidema.nl [172.20.1.10]) by hobbes.brasapen.org (Postfix) with ESMTP id 902A368B6; Thu, 20 Jan 2005 12:07:25 +0100 (CET) Received: by webmail.home.brasapen.org (Postfix, from userid 1001) id 7CF8F60D7; Thu, 20 Jan 2005 12:07:25 +0100 (CET) Date: Thu, 20 Jan 2005 12:07:25 +0100 From: Eilko Bos To: Ted Mittelstaedt Message-ID: <20050120110725.GA99151@webmail.home.brasapen.org> References: <41EF4A34.4020808@att.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i X-Bos-Zuidema-MailScanner-Information: Neem contact op met postmaster@bos-zuidema.nl voor meer informatie X-Bos-Zuidema-MailScanner: Found to be clean X-MailScanner-From: tafkam@brasapen.org cc: FreeBSD - questions cc: Jay O'Brien Subject: Re: Security for webserver behind router? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jan 2005 11:07:33 -0000 >From the keyboard of Ted Mittelstaedt, written on Wed, Jan 19, 2005 at 11:25:00PM -0800: > > I am running Apache 1.3.33, as you suggest I should. You say > > "as long as > > Apache is secure"; what should I do to be sure that Apache is secure? > > > > Nothing, you nor nobody can do this. All you can do is subscribe to > the Apache mailing list and if someone discovers a hole in Apache > at some point in the future, then you can immediately patch your > installation with the inevitable patch that will shortly follow. Don't forget that Apache's nature is offering content. What about unsafe PHP/CGI-scripts? You can secure Apache, but that doesn't help when your webapplication is a big hole to your system. Just my 0.2$c Grtz, -- Eilko.