From owner-freebsd-security@FreeBSD.ORG  Wed Jan 28 21:07:08 2015
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.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id BEE1072E
 for <freebsd-security@freebsd.org>; Wed, 28 Jan 2015 21:07:08 +0000 (UTC)
Received: from 1.mo2.mail-out.ovh.net (1.mo2.mail-out.ovh.net [46.105.63.121])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256
 bits)) (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 7D0EFE96
 for <freebsd-security@freebsd.org>; Wed, 28 Jan 2015 21:07:07 +0000 (UTC)
Received: from mail427.ha.ovh.net (b9.ovh.net [213.186.33.59])
 by mo2.mail-out.ovh.net (Postfix) with SMTP id 7CE69FFAA9C
 for <freebsd-security@freebsd.org>; Wed, 28 Jan 2015 20:47:40 +0100 (CET)
Received: from b0.ovh.net (HELO queueout) (213.186.33.50)
 by b0.ovh.net with SMTP; 28 Jan 2015 21:47:40 +0200
Received: from vau75-5-82-227-220-138.fbx.proxad.net (HELO ?127.0.0.1?)
 (leon.fazakerley@commerceo.com@82.227.220.138)
 by ns0.ovh.net with SMTP; 28 Jan 2015 21:47:39 +0200
Message-ID: <54C93CDB.8070909@tucoinfo.fr>
Date: Wed, 28 Jan 2015 20:47:39 +0100
From: "leon@tuco" <leon@tucoinfo.fr>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: freebsd-security@freebsd.org
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-15:02.kmem
References: <mailman.92.1422446402.71362.freebsd-security@freebsd.org>
 <20150128194012.37080238@hub.freebsd.org>
In-Reply-To: <20150128194012.37080238@hub.freebsd.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Ovh-Tracer-Id: 4385098663891245938
X-Ovh-Remote: 82.227.220.138 (vau75-5-82-227-220-138.fbx.proxad.net)
X-Ovh-Local: 213.186.33.20 (ns0.ovh.net)
X-OVH-SPAMSTATE: OK
X-OVH-SPAMSCORE: 20
X-OVH-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeejkedrvdekucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecuogetfedtledqtdduucdlvddtmd
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: 20
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrfeejkedrvdekucetufdoteggodetrfcurfhrohhfihhlvgemucfqggfjnecuuegrihhlohhuthemuceftddtnecuogetfedtledqtdduucdlvddtmd
X-BeenThere: freebsd-security@freebsd.org
X-Mailman-Version: 2.1.18-1
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: Wed, 28 Jan 2015 21:07:08 -0000

+1
and +10 to enable ALTQ in GENERIC in lieu of.

On 28/01/2015 20:39, Roger Marquis wrote:
>>> If SCTP is NOT compiled in the kernel, are you still vulnerable ?
>> >
>> >No -- we should have mentioned that too.  For GENERIC kernel however
>> >SCTP is compiled in.
> Should probably fix that too, in GENERIC, considering how little used this
> protocol is.