Date: Wed, 25 Feb 2015 10:11:56 -0800 From: jungle Boogie <jungleboogie0@gmail.com> To: freebsd-security@freebsd.org Cc: FreeBSD Security Advisories <security-advisories@freebsd.org> Subject: Re: FreeBSD Security Advisory FreeBSD-SA-15:05.bind Message-ID: <CAKE2PDt6YKOwc%2BnwM3A_A9b3s5arLfpx5U11cAX9Vkoy1nQS8g@mail.gmail.com> In-Reply-To: <201502250629.t1P6TSid007902@freefall.freebsd.org> References: <201502250629.t1P6TSid007902@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Security Officials of FreeBSD, On 24 February 2015 at 22:29, FreeBSD Security Advisories <security-advisories@freebsd.org> wrote: > 2) To update your vulnerable system via a binary patch: > > 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 My recommendation as a self check: Recommend users run freebsd-version -k and freebsd-version -u and indicate in the SA what they should see as a result. I know you don't want to give a false sense of security but when the result of following the prescribed advice is: freebsd-update install Installing updates...install: ///usr/src/crypto/openssl/util/mkbuildinf.pl: No such file or directory It may be ideal to let users know how to check their systems. -- ------- inum: 883510009027723 sip: jungleboogie@sip2sip.info xmpp: jungle-boogie@jit.si
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAKE2PDt6YKOwc%2BnwM3A_A9b3s5arLfpx5U11cAX9Vkoy1nQS8g>