From owner-freebsd-security@FreeBSD.ORG  Tue Sep 16 16:36:31 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 E6615E28
 for <freebsd-security@freebsd.org>; Tue, 16 Sep 2014 16:36:31 +0000 (UTC)
Received: from mx1.rsle.net (mx1.rsle.net [IPv6:2607:ff40:b0b::4])
 (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 A1519905
 for <freebsd-security@freebsd.org>; Tue, 16 Sep 2014 16:36:31 +0000 (UTC)
Received: from CLASSIFIED (CLASSIFIED [IPv6:2607:ff40:b0b::3:1415])
 (authenticated bits=0)
 by mx1.rsle.net (8.14.9/8.14.9) with ESMTP id s8GGaKuQ041743
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <freebsd-security@freebsd.org>; Tue, 16 Sep 2014 12:36:20 -0400 (EDT)
 (envelope-from freebsd-security@rsle.net)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.4 at antivirus.rsle.net
Message-ID: <541866FF.1070204@rsle.net>
Date: Tue, 16 Sep 2014 12:36:15 -0400
From: "R. Scott Evans" <freebsd-security@rsle.net>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.1.0
MIME-Version: 1.0
To: freebsd-security@freebsd.org
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:19.tcp
References: <20140916150742.GA1201@faust.sbb.rs>
In-Reply-To: <20140916150742.GA1201@faust.sbb.rs>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3
 (mx1.rsle.net [IPv6:2607:ff40:b0b::2]); Tue, 16 Sep 2014 12:36:20 -0400 (EDT)
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: Tue, 16 Sep 2014 16:36:32 -0000

On 09/16/14 11:07, Zoran Kolic wrote:
> Sorry to make a mistake, regarding the subject!!!
>
>> Systems running a RELEASE version of FreeBSD on the i386 or amd64
>> platforms can be updated via the freebsd-update(8) utility:
>>
>> # freebsd-update fetch
>> # freebsd-update install
>
> This is the question, I was intended to ask, since
> the patch method needs kernel recompile:
> do I need to recompile the kernel after freebsd-update?
> Sorry for the noise
>
>                              Zoran

The advisory solution offers 3 options... freebsd-update is the binary 
approach (option #3) that provides you a new updated generic kernel 
already compiled.  If you aren't using a generic kernel or want to patch 
and recompile your own, then you would use the option #2.

-scott