Mailing List Archive

Re: ClamAV? blog: ClamAV 0.103.2 security patch release
Hi there,

On Sat, 10 Apr 2021, Per Jessen wrote:

> When I built $SUBJ just now, I see
>
> libclammspack.so.0
> => /home/per/workspace/clamav-0.103.2/libclamav/.libs/libclammspack.so.0
>
> ie. with a fixed path ? How do I avoid that?

Is this before 'make install'?

After you install it I'd expect something more like

# ldd `which clamd-0.103.2-allmatchstream` | grep libclammspack
libclammspack.so.0 => /usr/local/lib/libclammspack.so.0 (0xb6734000)

If this is after install, exactly how did you build it?

Not sure this should be on the development list.

--

73,
Ged.
_______________________________________________

clamav-devel mailing list
clamav-devel@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-devel

Please submit your patches to our Github: https://github.com/Cisco-Talos/clamav-devel/pulls

Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml
Re: ClamAV? blog: ClamAV 0.103.2 security patch release [ In reply to ]
Hello again,

On Sun, 11 Apr 2021, Per Jessen wrote:

> Just to be clear - with 0.103.2:
>
> ldd /usr/lib64/libclamav.so
> linux-vdso.so.1 (0x00007ffcdb1a7000)
> libbz2.so.1 => /usr/lib64/libbz2.so.1 (0x00007fe0864ff000)
> libdl.so.2 => /lib64/libdl.so.2 (0x00007fe0862fb000)
> libclammspack.so.0 => /home/per/workspace/clamav-0.103.2/libclamav/.libs/libclammspack.so.0 (0x00007fe0860e8000)
> libssl.so.1.1 => /usr/lib64/libssl.so.1.1 (0x00007fe085e7c000)
> libcrypto.so.1.1 => /usr/lib64/libcrypto.so.1.1 (0x00007fe0859ee000)
> libz.so.1 => /lib64/libz.so.1 (0x00007fe0857d7000)
> libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007fe08554a000)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fe08532c000)
> libm.so.6 => /lib64/libm.so.6 (0x00007fe084ff4000)
> libc.so.6 => /lib64/libc.so.6 (0x00007fe084c3a000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fe086b16000)
>
> With e.g. 0.102.1
>
> ldd /usr/lib64/libclamav.so
> linux-vdso.so.1 (0x00007ffebd1f4000)
> libdl.so.2 => /lib64/libdl.so.2 (0x00007fe60e51e000)
> libclammspack.so.0 => /usr/lib64/libclammspack.so.0 (0x00007fe60e30b000)
> libssl.so.1.1 => /usr/lib64/libssl.so.1.1 (0x00007fe60e09f000)
> libcrypto.so.1.1 => /usr/lib64/libcrypto.so.1.1 (0x00007fe60dc11000)
> libz.so.1 => /lib64/libz.so.1 (0x00007fe60d9fa000)
> libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007fe60d76d000)
> libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fe60d54f000)
> libm.so.6 => /lib64/libm.so.6 (0x00007fe60d217000)
> libc.so.6 => /lib64/libc.so.6 (0x00007fe60ce5d000)
> /lib64/ld-linux-x86-64.so.2 (0x00007fe60eaec000)

On my clamd server, looking at the files from 0.103.2 in the build
directory and in the installed location:

$ ldd ./clamav-0.103.2/libclamav/.libs/libclamav.so | grep libclammspack
libclammspack.so.0 => /home/ged/clamav-0.103.2/libclamav/.libs/libclammspack.so.0 (0xb6bc4000)

$ ldd /usr/local/lib/libclamav.so | grep libclammspack
libclammspack.so.0 => /usr/local/lib/libclammspack.so.0 (0xb6b85000)

So the 'make install' fixed it up. I think you'd be much better off
doing a 'make install', even if you have to add an 'install-libs'
target in the makefile (there's already an install-everythingelse).

Or you could just ignore the other installed stuff, or delete it if
you really don't want it there.

--

73,
Ged.
_______________________________________________

clamav-devel mailing list
clamav-devel@lists.clamav.net
https://lists.clamav.net/mailman/listinfo/clamav-devel

Please submit your patches to our Github: https://github.com/Cisco-Talos/clamav-devel/pulls

Help us build a comprehensive ClamAV guide:
https://github.com/vrtadmin/clamav-faq

http://www.clamav.net/contact.html#ml