From owner-freebsd-security@FreeBSD.ORG  Thu Jun  5 20:12:34 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 9B9CDDAB
 for <freebsd-security@freebsd.org>; Thu,  5 Jun 2014 20:12:34 +0000 (UTC)
Received: from mx1.rsle.net (mx1.rsle.net [IPv6:2607:ff40:b0b::4])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 34AE824C9
 for <freebsd-security@freebsd.org>; Thu,  5 Jun 2014 20:12:34 +0000 (UTC)
Received: from prometheus.rsle.net (UNKNOWN [206.162.203.14] (may be forged))
 (authenticated bits=0)
 by mx1.rsle.net (8.14.7/8.14.7) with ESMTP id s55KCRBR044310
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <freebsd-security@freebsd.org>; Thu, 5 Jun 2014 16:12:27 -0400 (EDT)
 (envelope-from freebsd-security@rsle.net)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.98.3 at antivirus.rsle.net
Message-ID: <5390CF26.2050401@rsle.net>
Date: Thu, 05 Jun 2014 16:12:22 -0400
From: "R. Scott Evans" <freebsd-security@rsle.net>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:24.0) Gecko/20100101 Thunderbird/24.5.0
MIME-Version: 1.0
To: freebsd-security@freebsd.org
Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:14.openssl
References: <201406051316.s55DGtwI041948@freefall.freebsd.org>
 <5390BA3F.5060202@rsle.net> <44ha3zfb36.fsf@lowell-desk.lan>
In-Reply-To: <44ha3zfb36.fsf@lowell-desk.lan>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.4.3
 (mx1.rsle.net [206.162.201.2]); Thu, 05 Jun 2014 16:12:27 -0400 (EDT)
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: Thu, 05 Jun 2014 20:12:34 -0000

On 06/05/14 14:46, Lowell Gilbert wrote:
> "R. Scott Evans" <freebsd-security@rsle.net> writes:
>
>> After updating via the binary patch method with freebsd-update, uname
>> still reports 9.2-RELEASE-p7 even after reboot.  An additional
>> freebsd-update after this initial update however does not report
>> anything new to update (aside from the ongoing persistent
>> /boot/kernel/linker.hints).
>
> Makes sense. The kernel doesn't use SSL internally.

I would agree except the advisory says this problem is corrected in 
9.2-RELEASE-p8.  Likewise, the freebsd-update explicitly says "The 
following files will be updated as part of updating to 9.2-RELEASE-p8".

-scott