From owner-freebsd-security Mon Jan 24 0:29:37 2000 Delivered-To: freebsd-security@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 839FA150BA for ; Mon, 24 Jan 2000 00:29:32 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12Ces0-000G37-00; Mon, 24 Jan 2000 10:29:08 +0200 From: Sheldon Hearn To: "Dan Seafeldt, AZ.COM System Administrator" Cc: security@FreeBSD.ORG Subject: Re: Microsoft Windows Update In-reply-to: Your message of "Sat, 22 Jan 2000 00:55:02 PST." Date: Mon, 24 Jan 2000 10:29:08 +0200 Message-ID: <61696.948702548@axl.noc.iafrica.com> Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 22 Jan 2000 00:55:02 PST, "Dan Seafeldt, AZ.COM System Administrator" w rote: > http://windowsupdate.microsoft.com [...] > Although if FreeBSD implemented something similar to this, it might > be nice to consider when public notification of the nature of the > problem before, during or after a particular fix was automatically > disseminated would be appropriate. FreeBSD already has the resources required to deliver this service. We have several easy ways to keep the system up-to-date with the latest and greatest fixes (CVS, CVSup, CTM). We have a mailing list on which all these fixes are described (cvs-all). And we have a mailing list on which official announcements are made once serious security problems have been investigated and solutions made available (freebsd-security). If you'd like to set up a web site on which you provide what you consider to be a digest of significant issues fixed but not announced on freebsd-security, you're welcome to do that. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message