On 10/4/10 8:29 PM, Al Varnell wrote:
Could it be that clamd was somehow compiled with 1.0.2?
It appears that your library is 1.0.2 regardless of what the binary might be.
Did you ever do a restore of you /lib? That's most frequently how libs get
mysteriously backleveled. Assuming it was ever upgraded to 1.0.5.
So again, how come clamd says it loads 1.0.2
Load command 13
cmd LC_LOAD_DYLIB
cmdsize 52
name /usr/lib/libbz2.1.0.dylib (offset 24)
time stamp 2 Wed Dec 31 16:00:02 1969
current version 1.0.2
compatibility version 1.0.0
while bzip2 loads 1.0.5?
This is where I usually say something clever like "something we're sure of is
wrong". I'm out of ideas.
I guess my last wonderment would be to speculate your clamd was static linked to
older libs, but it's a swag as I don't recall ever using otool on static linked
binaries so don't know what it would say about its pedigree.
dp
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
