From owner-freebsd-current@FreeBSD.ORG Mon May 26 01:33:55 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9DEC437B401; Mon, 26 May 2003 01:33:55 -0700 (PDT) Received: from vhost109.his.com (vhost109.his.com [216.194.225.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 823C143F85; Mon, 26 May 2003 01:33:54 -0700 (PDT) (envelope-from brad.knowles@skynet.be) Received: from [10.0.1.2] (localhost.his.com [127.0.0.1]) by vhost109.his.com (8.12.6p2/8.12.3) with ESMTP id h4Q8XptS013408; Mon, 26 May 2003 04:33:53 -0400 (EDT) (envelope-from brad.knowles@skynet.be) Mime-Version: 1.0 X-Sender: bs663385@pop.skynet.be Message-Id: In-Reply-To: <20030526053120.GB1941@athlon.pn.xcllnt.net> References: <20030525061524.H30007@sasami.jurai.net> <20030525084629.R30007@sasami.jurai.net> <20030525222955.GA826@athlon.pn.xcllnt.net> <20030525190744.A86964@sasami.jurai.net> <20030526001924.GA1272@athlon.pn.xcllnt.net> <20030525202140.Y86964@sasami.jurai.net> <20030526053120.GB1941@athlon.pn.xcllnt.net> Date: Mon, 26 May 2003 10:28:42 +0200 To: Marcel Moolenaar From: Brad Knowles Content-Type: text/plain; charset="us-ascii" ; format="flowed" cc: current@FreeBSD.ORG cc: "Matthew N. Dodd" Subject: Re: Preliminary ELF prebinding patches available. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 May 2003 08:33:56 -0000 At 10:31 PM -0700 2003/05/25, Marcel Moolenaar wrote: > Hence, prebind information is decoupled from the executable. One > of the more obvious complexities is the fact that the naming scheme > is such that multiple binaries can have the same prebind cache file. > The collision is currently not handled, other than making sure that > the prebind information for binary A1 is not used by binary A2. But > other complexities exist. What if by some unlucky draw of faith you > have two totally independent executables that both resolve to the > same prebind file *and* happen to have the same build ID? You have > an undetectable collision. How painful would it be to do a checksum (ideally, MD5 hash) of the binary in question? Or at least recording path to the binary within the prebind cache file? Or maybe file metadata like the ownership, permissions, and date/time stamp? -- Brad Knowles, "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -Benjamin Franklin, Historical Review of Pennsylvania. GCS/IT d+(-) s:+(++)>: a C++(+++)$ UMBSHI++++$ P+>++ L+ !E-(---) W+++(--) N+ !w--- O- M++ V PS++(+++) PE- Y+(++) PGP>+++ t+(+++) 5++(+++) X++(+++) R+(+++) tv+(+++) b+(++++) DI+(++++) D+(++) G+(++++) e++>++++ h--- r---(+++)* z(+++)