From owner-freebsd-security Tue Oct 1 14: 4:14 2002 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 3A5C437B401 for ; Tue, 1 Oct 2002 14:04:13 -0700 (PDT) Received: from pogo.caustic.org (caustic.org [64.163.147.186]) by mx1.FreeBSD.org (Postfix) with ESMTP id D811B43E77 for ; Tue, 1 Oct 2002 14:04:11 -0700 (PDT) (envelope-from jan@caustic.org) Received: from localhost (jan@localhost) by pogo.caustic.org (8.11.6/8.11.6) with ESMTP id g91L3CV90978; Tue, 1 Oct 2002 14:03:12 -0700 (PDT) (envelope-from jan@caustic.org) Date: Tue, 1 Oct 2002 14:03:11 -0700 (PDT) From: "f.johan.beisser" To: Brett Glass Cc: Matthew Dillon , Matt Piechota , Aaron Namba , Subject: Re: RE: Is FreeBSD's tar susceptible to this? In-Reply-To: <4.3.2.7.2.20021001133156.03609ec0@localhost> Message-ID: <20021001134719.S67581-100000@pogo.caustic.org> 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 Tue, 1 Oct 2002, Brett Glass wrote: > I agree. And while folks are correct that licensing is not the only issue > here, why not take the opportunity to adopt something BSD-licensed instead? > At the same time, it would be possible to integrate bzip instead of invoking > it as a separate process. This would make it more efficient when we go to > bzip for ports and packages. Brett, i'm going to thank you on behalf of the various BSD projects for volunteering your time and skills in creating a BSD licensed tar that is GNU-tar compatable. should i expect this before or after the BSD licensed C compiler? -------/ f. johan beisser /--------------------------------------+ http://caustic.org/~jan jan@caustic.org "John Ashcroft is really just the reanimated corpse of J. Edgar Hoover." -- Tim Triche To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message