From owner-freebsd-security Mon May 15 9:21: 3 2000 Delivered-To: freebsd-security@freebsd.org Received: from modemcable127.61-201-24.mtl.mc.videotron.net (modemcable127.61-201-24.mtl.mc.videotron.net [24.201.61.127]) by hub.freebsd.org (Postfix) with SMTP id E1F1337B6B6 for ; Mon, 15 May 2000 09:20:59 -0700 (PDT) (envelope-from patrick@mindstep.com) Received: (qmail 48153 invoked from network); 15 May 2000 16:20:58 -0000 Received: from patrak.local.mindstep.com (HELO PATRAK) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 15 May 2000 16:20:58 -0000 Message-ID: <052001bfbe89$8087e590$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: References: <200005131542.XAA13898@netrinsics.com> <392017D7.C22BDB57@softweyr.com> <20000515163740.M83350@naiad.eclipse.net.uk> Subject: Re: New packaging tool (was Re: Applying patches with out a compiler) Date: Mon, 15 May 2000 12:20:36 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, From: "Stuart Henderson" > On Mon, May 15, 2000 at 09:29:27AM -0600, Wes Peters wrote: > > Got a handy pointer to the JAR spec? > > http://java.sun.com/products/jdk/1.1/docs/guide/jar/ > http://docs.iplanet.com/docs/manuals/signedobj/jarfile/jar.htm > After looking at the jar "specification", it only offers a way to resolve the "signing" problem. While this is good, I wonder how well extensions to support the other features I am looking at implemented would be supported by other "jar openers". Is this the way we should go: - create a "libjar" that can open and parse the content of the manifest in a reasonable way - (re)create the packaging tool so that it obtains its information from the jar file. The question is also: how do we go about manifest extensions in order to support all of what we needed ? - do we just create a set of "FreeBSD-specific" header/value pairs ? - are there more headers specified for the JAR files ? It looks to me that using this file format could be worthwhile, but to provide the level of functionality that we have currently with pkg_* it will require a good deal of non-standard extensions. So are there any more complete specs for the jar files ? Should we pursue in that direction ? Patrick. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message