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, <brad.knowles_at_skynet.be> "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(+++)Received on Sun May 25 2003 - 23:33:55 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:37:09 UTC