Date: Thu, 5 Jun 2014 21:41:15 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-security@freebsd.org Subject: Re: FreeBSD Security Advisory FreeBSD-SA-14:14.openssl Message-ID: <20140605214115.3797b3ee@gumby.homeunix.com> In-Reply-To: <5390CF26.2050401@rsle.net> References: <201406051316.s55DGtwI041948@freefall.freebsd.org> <5390BA3F.5060202@rsle.net> <44ha3zfb36.fsf@lowell-desk.lan> <5390CF26.2050401@rsle.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 05 Jun 2014 16:12:22 -0400 R. Scott Evans wrote: > 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". The version is recorded in the kernel; freebsd-update doesn't update the kernel just to update the version.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140605214115.3797b3ee>