From owner-freebsd-security@FreeBSD.ORG Wed Feb 25 18:11:57 2015 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BDCDA190; Wed, 25 Feb 2015 18:11:57 +0000 (UTC) Received: from mail-ob0-x236.google.com (mail-ob0-x236.google.com [IPv6:2607:f8b0:4003:c01::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 8389EEF1; Wed, 25 Feb 2015 18:11:57 +0000 (UTC) Received: by mail-ob0-f182.google.com with SMTP id nt9so5475374obb.13; Wed, 25 Feb 2015 10:11:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=3Vhd1rIKVctDqTTMzy9nNXA5LuV3Y1/l91PQ0A/oLFc=; b=bbspkIZtwQJAmD8rV7f0pt1Kwz5EEemQJi6mJUay3on4Tum9ErKmRBLaiSYfJEUXwY 785RBNbch/c0//DP3mcRFt+sJVd8eyj9C6xcMZn/9vkkBblEJMaRI9T1+fztrEfE0FzY kMTH9qoq0507bKcGfzZVoUc3dF0iCZDAku8e4v1T8+aGcdMf076TP55sM5jH4jDVH3Ci GOqqNOVywrjNxgGIRFWPjSm3nlKlflY7O9e2KoqRGbMGvI7YcfJ7mtwzgOEkfXdqSF8T OUO5XSJb4B3fAKEkS1VIVrhao0WrOwc1yiH7H62Amz282JXixTbtpYgWNuioZOwpKzcC iOBQ== MIME-Version: 1.0 X-Received: by 10.60.63.39 with SMTP id d7mr3186569oes.4.1424887916598; Wed, 25 Feb 2015 10:11:56 -0800 (PST) Received: by 10.182.247.74 with HTTP; Wed, 25 Feb 2015 10:11:56 -0800 (PST) In-Reply-To: <201502250629.t1P6TSid007902@freefall.freebsd.org> References: <201502250629.t1P6TSid007902@freefall.freebsd.org> Date: Wed, 25 Feb 2015 10:11:56 -0800 Message-ID: Subject: Re: FreeBSD Security Advisory FreeBSD-SA-15:05.bind From: jungle Boogie To: freebsd-security@freebsd.org Content-Type: text/plain; charset=UTF-8 Cc: FreeBSD Security Advisories X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Feb 2015 18:11:57 -0000 Hi Security Officials of FreeBSD, On 24 February 2015 at 22:29, FreeBSD Security Advisories 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