From owner-freebsd-security@FreeBSD.ORG Sun Nov 18 19:28:15 2012 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 88481CE1 for ; Sun, 18 Nov 2012 19:28:15 +0000 (UTC) (envelope-from brett@lariat.org) Received: from lariat.net (lariat.net [66.62.230.51]) by mx1.freebsd.org (Postfix) with ESMTP id 2777E8FC08 for ; Sun, 18 Nov 2012 19:28:14 +0000 (UTC) Received: from Toshi.lariat.org (IDENT:ppp1000.lariat.net@lariat.net [66.119.58.2] (may be forged)) by lariat.net (8.9.3/8.9.3) with ESMTP id MAA15211 for ; Sun, 18 Nov 2012 12:28:13 -0700 (MST) Message-Id: <201211181928.MAA15211@lariat.net> X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Sun, 18 Nov 2012 12:28:06 -0700 To: freebsd-security@freebsd.org From: Brett Glass Subject: How much will intrusion delay 9.1-RELEASE? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Security issues \[members-only posting\]" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 19:28:15 -0000 How much will the current security issue delay 9.1-RELEASE? I do want to see the integrity of the code protected, but must plan server updates, which I'd hoped to do over US Thanksgiving. (9.0-RELEASE is now within a couple of months of EOL unless it's extended.) --Brett Glass