From owner-freebsd-current  Fri Aug  7 09:24:13 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA01056
          for freebsd-current-outgoing; Fri, 7 Aug 1998 09:24:13 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA01035
          for <freebsd-current@freebsd.org>; Fri, 7 Aug 1998 09:24:08 -0700 (PDT)
          (envelope-from tom@uniserve.com)
Received: from shell.uniserve.ca [204.244.186.218] 
	by pop.uniserve.com with smtp (Exim 1.82 #4)
	id 0z4pIy-0003Xy-00; Fri, 7 Aug 1998 09:23:48 -0700
Date: Fri, 7 Aug 1998 09:23:47 -0700 (PDT)
From: Tom <tom@uniserve.com>
X-Sender: tom@shell.uniserve.ca
To: Dag-Erling Coidan =?iso-8859-1?Q?Sm=F8rgrav?=  <dag-erli@ifi.uio.no>
cc: freebsd-current@FreeBSD.ORG
Subject: Re: memory leaks in libc
In-Reply-To: <xzpemusopim.fsf@hrotti.ifi.uio.no>
Message-ID: <Pine.BSF.3.96.980807092226.17170C-100000@shell.uniserve.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


> > apache on a Linux machine here is still thinking about wheterh or not to 
> > return 100M, time to test it on my home FreeBSD server :-)
> 
> So maybe it's time to switch to thttpd.
> 
> Seriously, Apache should not rely on getenv() / setenv(). It should

  It doesn't.  Whatever is being exploited, it isn't that.

  Besides there are tons of such overload DoS attacks for web servers.
How about just open connection and do nothing?  That works on every web
server.

Tom


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message