From owner-freebsd-audit Mon Jan 31 13:22:45 2000 Delivered-To: freebsd-audit@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A7BDC14C05 for ; Mon, 31 Jan 2000 13:22:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA04736; Mon, 31 Jan 2000 14:22:30 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA08153; Mon, 31 Jan 2000 14:22:38 -0700 (MST) Message-Id: <200001312122.OAA08153@harmony.village.org> To: matt@csis.gvsu.edu Subject: Re: Some programs that could use some work Cc: Mike Heffner , FreeBSD-audit In-reply-to: Your message of "Mon, 31 Jan 2000 16:18:31 EST." <20000131161831.A75560@badmofo> References: <20000131161831.A75560@badmofo> Date: Mon, 31 Jan 2000 14:22:37 -0700 From: Warner Losh Sender: owner-freebsd-audit@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000131161831.A75560@badmofo> matt@csis.gvsu.edu writes: : Does the recent code freeze slow done the audit process? It sounded : like only essential patches will be added. Just when I have time to : start working :) Well, the FreeBSD security officer's word (eg mine) has a lot of pull in the area of security when it comes to changes during this code freeze. If there are security problems, or potential problems, then the SO will do what he can to make sure they get into 4.0. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message