From owner-freebsd-security@freebsd.org Tue Nov 21 06:36:32 2017 Return-Path: Delivered-To: freebsd-security@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 6065ADE4933 for ; Tue, 21 Nov 2017 06:36:32 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from host64.shmhost.net (host64.shmhost.net [IPv6:2a01:4f8:a0:51d7::103:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 2A1C424A2 for ; Tue, 21 Nov 2017 06:36:32 +0000 (UTC) (envelope-from franco@lastsummer.de) Received: from [192.168.10.2] (095-097-023-077.static.chello.nl [95.97.23.77]) by host64.shmhost.net (Postfix) with ESMTPSA id 5512016903E; Tue, 21 Nov 2017 07:36:30 +0100 (CET) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: freebsd-update EoL "warning" prevents installing latest SAs From: Franco Fichtner In-Reply-To: Date: Tue, 21 Nov 2017 07:36:29 +0100 Cc: freebsd-security Content-Transfer-Encoding: 7bit Message-Id: <5ACFF7B8-460E-473F-ADA0-D9200587FC55@lastsummer.de> References: To: User X-Mailer: Apple Mail (2.3273) X-Virus-Scanned: clamav-milter 0.99.2 at host64.shmhost.net X-Virus-Status: Clean X-Spam-Flag: NO X-Spam-Score: -1.0 X-Spam-Status: No score=-1.0 tagged_above=10.0 required=10.0 tests=[ALL_TRUSTED] X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Nov 2017 06:36:32 -0000 > On 21. Nov 2017, at 7:31 AM, User wrote: > > The updates install fine here even if the eol warning is showing. The uname > only updates if the kernel updates for patch levels. I find that hard to believe unless there is a caching issue with the EoL date, the return clearly uses "1" which means fail in the fetch phase. Ah, but then again this is more likely a side effect of using: # freebsd-update fetch install In any case, fetch should now fail if it fetched updates... Cheers, Franco