From owner-freebsd-security@FreeBSD.ORG  Tue May 27 18:43:38 2014
Return-Path: <owner-freebsd-security@FreeBSD.ORG>
Delivered-To: freebsd-security@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 99921A39
 for <freebsd-security@freebsd.org>; Tue, 27 May 2014 18:43:38 +0000 (UTC)
Received: from outgoing.tristatelogic.com (segfault.tristatelogic.com
 [69.62.255.118]) by mx1.freebsd.org (Postfix) with ESMTP id 82FB42888
 for <freebsd-security@freebsd.org>; Tue, 27 May 2014 18:43:37 +0000 (UTC)
Received: from segfault-nmh-helo.tristatelogic.com (localhost [127.0.0.1])
 by segfault.tristatelogic.com (Postfix) with ESMTP id 4B33D3ADD6
 for <freebsd-security@freebsd.org>; Tue, 27 May 2014 11:43:37 -0700 (PDT)
From: "Ronald F. Guilmette" <rfg@tristatelogic.com>
To: freebsd-security@freebsd.org
Subject: Re: NEVERMIND!
In-Reply-To: <867g57bq9o.fsf@nine.des.no>
Date: Tue, 27 May 2014 11:43:37 -0700
Message-ID: <5833.1401216217@server1.tristatelogic.com>
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: "Security issues \[members-only posting\]"
 <freebsd-security.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-security/>
List-Post: <mailto:freebsd-security@freebsd.org>
List-Help: <mailto:freebsd-security-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-security>, 
 <mailto:freebsd-security-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 27 May 2014 18:43:38 -0000


In message <867g57bq9o.fsf@nine.des.no>, 
=?utf-8?Q?Dag-Erling_Sm=C3=B8rgrav?= <des@des.no> wrote:

>"Ronald F. Guilmette" <rfg@tristatelogic.com> writes:
>> So should I file a PR on this, or what?
>
>*shrug*
>
>I think this falls under the same heading as a fork bomb -

Ah!  But unlike unlimited syslogging, there _is_ already something
in place that limits the damage from a "fork bomb":

% limits
Resource limits (current):
  ...
  maxprocesses             5547        <=====================
  ...