From owner-freebsd-security Tue Mar 12 12:39:15 2002 Delivered-To: freebsd-security@freebsd.org Received: from vapour.net (vapour.net [198.96.117.180]) by hub.freebsd.org (Postfix) with ESMTP id 82E3C37B404 for ; Tue, 12 Mar 2002 12:39:07 -0800 (PST) Received: from vapour.net (vapour.net [198.96.117.180]) by vapour.net (8.11.6/8.11.6) with ESMTP id g2CKW0b16445; Tue, 12 Mar 2002 15:32:01 -0500 (EST) (envelope-from batsy@vapour.net) Date: Tue, 12 Mar 2002 15:31:56 -0500 (EST) From: batz To: Christopher Schulte Cc: lewwid , freebsd-security@FreeBSD.ORG, Max Mouse Subject: Re: PHP 4.1.2 In-Reply-To: <5.1.0.14.0.20020311102243.01b00c38@pop3s.schulte.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 11 Mar 2002, Christopher Schulte wrote: :>Would it be useful to have a security branch from which people could cvsup :>security patches? : :>Does such a system exist just for security updates? : :For ports? No. I would volunteer as maintainer as it isn't too far removed from my day job to handle something like this. :) On a simple level, it could just be a tree with copies of updated ports with patches that people could cvsup from a given site. What other features would people want from such a service? Though I suppose cvsup'ing the ports tree on a regular basis would accomplish the same thing, it might be nice to do it on a security specific basis. A vulnerability in zlib suggests that it would be worth having a specific method for users to update all ports that use zlib, no? Cheers, -- batz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message