From owner-freebsd-security@FreeBSD.ORG Thu Sep 18 08:01:22 2003 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B37B16A4B3; Thu, 18 Sep 2003 08:01:22 -0700 (PDT) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29F8D43FBF; Thu, 18 Sep 2003 08:01:19 -0700 (PDT) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id CED5A5482B; Thu, 18 Sep 2003 10:01:18 -0500 (CDT) Received: by madman.celabo.org (Postfix, from userid 1001) id 5FBDF6D454; Thu, 18 Sep 2003 10:01:18 -0500 (CDT) Date: Thu, 18 Sep 2003 10:01:18 -0500 From: "Jacques A. Vidrine" To: "Bruce A. Mah" Message-ID: <20030918150118.GF32994@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , "Bruce A. Mah" , Nielsen , freebsd-security@freebsd.org References: <3F68FE17.5050700@memberwebs.com> <200309180340.h8I3e8Hl042756@intruder.kitchenlab.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200309180340.h8I3e8Hl042756@intruder.kitchenlab.org> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.4i-ja.1 cc: freebsd-security@freebsd.org Subject: Re: ftp.freebsd.org out of date? (WRT security advisories) X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 15:01:22 -0000 On Wed, Sep 17, 2003 at 08:40:08PM -0700, Bruce A. Mah wrote: > I'm not sure what's a good solution to this. I know that security-team > is aware of the problem, in fact it came up in the security-officer BoF > at BSDCon. I think the end result was that I'm basically willing to manually push updates to any mirrors to which I have access. I have been pushing them to ftp and ftp2, but (as I posted in a recent message), recent events have mucked this up a bit. > (One possibility might be to put the advisories on the Web site and > force an update immediately after an advisory is issued. I do this > during the late stages of a release cycle to push out the release > announcements and release notes. The problem with this, however, is > that everyone is conditioned to look to the FTP sites for advisories.) I wouldn't mind having the advisories and patches live on HTTP also. It is arguably more convenient for more people. I wouldn't want to have to go through CVS first to publish the patches or advisory however. Cheers, -- Jacques Vidrine . NTT/Verio SME . FreeBSD UNIX . Heimdal nectar@celabo.org . jvidrine@verio.net . nectar@freebsd.org . nectar@kth.se