From owner-freebsd-security@FreeBSD.ORG Thu Jun 5 18:47:07 2014 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E4E1515A for ; Thu, 5 Jun 2014 18:47:07 +0000 (UTC) Received: from be-well.ilk.org (be-well.ilk.org [23.30.133.173]) by mx1.freebsd.org (Postfix) with ESMTP id BE2702DAE for ; Thu, 5 Jun 2014 18:47:07 +0000 (UTC) Received: from lowell-desk.lan (lowell-desk.lan [172.30.250.41]) by be-well.ilk.org (Postfix) with ESMTP id A1CA533C22; Thu, 5 Jun 2014 14:46:56 -0400 (EDT) Received: by lowell-desk.lan (Postfix, from userid 1147) id E517039813; Thu, 5 Jun 2014 14:46:54 -0400 (EDT) From: Lowell Gilbert To: "R. Scott Evans" Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:14.openssl References: <201406051316.s55DGtwI041948@freefall.freebsd.org> <5390BA3F.5060202@rsle.net> Date: Thu, 05 Jun 2014 14:46:53 -0400 In-Reply-To: <5390BA3F.5060202@rsle.net> (R. Scott Evans's message of "Thu, 05 Jun 2014 14:43:11 -0400") Message-ID: <44ha3zfb36.fsf@lowell-desk.lan> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain Cc: freebsd-security@freebsd.org X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Jun 2014 18:47:08 -0000 "R. Scott Evans" 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.