From owner-freebsd-security@FreeBSD.ORG Tue Jun 17 22:56:56 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 B0411F5B for ; Tue, 17 Jun 2014 22:56:56 +0000 (UTC) Received: from mx.morhold.ru (master.morhold.ru [89.188.102.188]) (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 1AA90282C for ; Tue, 17 Jun 2014 22:56:54 +0000 (UTC) Received: from [127.0.0.1] (mx [192.168.0.3] (may be forged)) by mx.morhold.ru (8.14.5/8.14.5) with ESMTP id s5HMbSan023565 for ; Wed, 18 Jun 2014 02:37:29 +0400 (MSK) (envelope-from freebsd-security@morhold.ru) Message-ID: <53A0C324.20200@morhold.ru> Date: Wed, 18 Jun 2014 02:37:24 +0400 From: Morhold User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: freebsd-security@freebsd.org Subject: Re: freebsd-update.conf IgnorePaths linker.hints not working References: <5382A982.6090304@calorieking.com> <86vbssr665.fsf@nine.des.no> <538494E8.2060302@rsle.net> <5386957E.2070000@calorieking.com> In-Reply-To: <5386957E.2070000@calorieking.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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: Tue, 17 Jun 2014 22:56:56 -0000 29.05.2014 6:03, Gregory Orange пишет: > On 27/05/14 21:36, R. Scott Evans wrote: >> On 05/26/14 10:00, Dag-Erling Smørgrav wrote: >>> This was supposed to be fixed by the following errata notice: >>> http://www.freebsd.org/security/advisories/FreeBSD-EN-14:04.kldxref.asc >> >> Well it is still broken after the 9.2-RELEASE-p6 also in that errata. >> >> The relevant thread in freebsd-questions: >> http://lists.freebsd.org/pipermail/freebsd-questions/2014-May/258238.html >> > > I'm left wondering what to do next: > * Should I simply delete linker.hints - would that cause unwanted > behaviour? > * Should I instead move linker.hints aside before freebsd-update cron > & freebsd-update install, then move it back again? That seems to work > on a manual test, but seems ugly. > * Should I post an official PR somewhere? > > Greg. > _______________________________________________ > freebsd-security@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-security > To unsubscribe, send any mail to > "freebsd-security-unsubscribe@freebsd.org" > Same here with 9.1-RELEASE-p14: # freebsd-update fetch ... The following files will be updated as part of updating to 9.1-RELEASE-p15: /boot/kernel/linker.hints # So I just did like this: - copied /usr/sbin/freebsd-update to /usr/sbin/freebsd-update,my - applied to /usr/sbin/freebsd-update,my the following patch: --- /usr/sbin/freebsd-update 2014-06-18 02:04:54.000000000 +0400 +++ /usr/sbin/freebsd-update,my 2014-06-18 02:08:12.000000000 +0400 @@ -2078,6 +2078,13 @@ # Fetch files. fetch_files || return 1 + mv INDEX-PRESENT INDEX-PRESENT,orig + grep -v '/boot/kernel/linker.hints' INDEX-PRESENT,orig > INDEX-PRESENT + rm INDEX-PRESENT,orig + mv INDEX-NEW INDEX-NEW,orig + grep -v '/boot/kernel/linker.hints' INDEX-NEW,orig > INDEX-NEW + rm INDEX-NEW,orig + # Create and populate install manifest directory; and report what # updates are available. fetch_create_manifest || return 1 - in /etc/crontab replaced "freebsd-update cron" to "freebsd-update,my cron" Now waiting what will happen after.