No updates rsync for 15.0?

Nobby6 · 06-22-2022, 06:21 PM

Wayne Davison via rsync

Sat, Apr 16, 7:12 AM

to rsync-announce, rsync
I have released rsync 3.2.4. Another typical release with both bug fixes and some enhancements. It also contains a security fix for the bundled zlib 1.2.8, which may or may not be used in your particular build configuration.

To see a summary of all the recent changes, visit this link:

https://rsync.samba.org/ftp/rsync/NEWS#3.2.4

You can download the source tar file and its signature from here:

https://rsync.samba.org/ftp/rsync/rsync-3.2.4.tar.gz
https://rsync.samba.org/ftp/rsync/rs...2.4.tar.gz.asc

rkelsen · 06-23-2022, 06:06 AM

I don't think rsync uses the bundled zlib. I'm not 100% sure though, because there's nothing in the SlackBuild about it.

Code:

rob@slackxps:~$ ldd /usr/bin/rsync
        linux-vdso.so.1 (0x00007ffd780a9000)
        libattr.so.1 => /lib64/libattr.so.1 (0x00007fe68e1d3000)
        libacl.so.1 => /lib64/libacl.so.1 (0x00007fe68e1c8000)
        libpopt.so.0 => /lib64/libpopt.so.0 (0x00007fe68e1b9000)
        liblz4.so.1 => /usr/lib64/liblz4.so.1 (0x00007fe68e186000)
        libzstd.so.1 => /lib64/libzstd.so.1 (0x00007fe68e0c8000)
        libxxhash.so.0 => /usr/lib64/libxxhash.so.0 (0x00007fe68e0bc000)
        libcrypto.so.1.1 => /lib64/libcrypto.so.1.1 (0x00007fe68ddd5000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fe68dbf6000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fe68dbd5000)
        libz.so.1 => /lib64/libz.so.1 (0x00007fe68dbbb000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fe68dbb6000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fe68e20f000)
rob@slackxps:~$

Looks like it's linked to zlib-1.2.12 to me.

Petri Kaukasoina · 06-23-2022, 06:47 AM

Quote:

Originally Posted by rkelsen

I don't think rsync uses the bundled zlib.

Looks like it's linked to zlib-1.2.12 to me.

No, it's not:

Code:

$ readelf -a /usr/bin/rsync|grep NEEDED
 0x0000000000000001 (NEEDED)             Shared library: [libattr.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libacl.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libpopt.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [liblz4.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libzstd.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libxxhash.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libcrypto.so.1.1]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]

It's libcrypto which links to the system libz:

Code:

$ readelf -a /lib64/libcrypto.so.1.1 |grep NEEDED
 0x0000000000000001 (NEEDED)             Shared library: [libz.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libdl.so.2]
 0x0000000000000001 (NEEDED)             Shared library: [libpthread.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]

So, ldd is not a good tool here.

If you run the slackbuild script, you can see that it compiles zlib-1.2.8 in subdirectory zlib, and links statically against it. But if you add --without-included-zlib to configure, it will not compile the old zlib, but links against the system zlib (1.2.12), like this:

Code:

 0x0000000000000001 (NEEDED)             Shared library: [libattr.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libacl.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libz.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libpopt.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [liblz4.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libzstd.so.1]
 0x0000000000000001 (NEEDED)             Shared library: [libxxhash.so.0]
 0x0000000000000001 (NEEDED)             Shared library: [libcrypto.so.1.1]
 0x0000000000000001 (NEEDED)             Shared library: [libc.so.6]