On Fri, Feb 25, 2011 at 3:49 PM, Jeff Johnson <n3...@mac.com> wrote: > > On Feb 25, 2011, at 9:40 AM, Mark Hatle wrote: > >> On 2/24/11 10:41 PM, Jeff Johnson wrote: >>> >>> On Feb 24, 2011, at 11:14 PM, Mark Hatle wrote: >>> >>>> I'm trying to validate prelinked binaries and I'm getting a somewhat >>>> strange result: >>>> >>>> ........ /bin >>>> S.?..... /bin/bash >>>> ........ /bin/bashbug >>>> >>>> The macro setting being used is: >>>> >>>> %__prelink_undo_cmd /usr/sbin/prelink prelink -y library >>>> >>>> I'm not sure what the '?' indicates, but I suspect it's some type of a >>>> failure >>>> to get the information from the prelinker. >>>> >>> >>> Hmmm ... I'm pretty sure prelink affects only libraries, not executables. >>> It has been years ... >> >> Prelink affects any ELF executable. But it doesn't do much good on >> executables > > Well "executable" and "library" is kinda blurry these days. > > Dunno what the correct technical term is. The engineering test for > prelinked can be read from the code. > > But "traditionally" its libraries, and I'm surprised at seeing/hearing > a /bin/bash prelink issue in RPM.
I not. I have in some project to disable prelinking system wide for implementing a centralizated system integrity mononitoring (also discussed by (the other)me some time ago on fedora-devel). In reality only recently prelink had corrected(by Jakub) also a bug for dropping file system capability on linux, and this bug was not only on "library" (https://bugzilla.redhat.com/show_bug.cgi?id=649972). Regards Regards > > 73 de Jeff > > ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List rpm-devel@rpm5.org
