lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 13 Jul 2009 19:22:51 +0200 (CEST)
From:	Peter Breitenlohner <peb@...mu.mpg.de>
To:	Karel Zak <kzak@...hat.com>
cc:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org,
	util-linux-ng@...r.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng v2.16-rc2 -- shlib versions

On Mon, 13 Jul 2009, Peter Breitenlohner wrote:

> On Thu, 2 Jul 2009, Karel Zak wrote:
>
>> The second util-linux-ng 2.16 release candidate is available at
>>
>>   ftp://ftp.kernel.org/pub/linux/utils/util-linux-ng/v2.16/
>> 
>> Feedback and bug reports, as always, are welcomed.
>
> Hi Karel,
>
> I just tried to build util-linux-ng-2.16-rc2 (i686/x86_64 linux-gnu
> with gcc-3.4.6, libc-2.3.6), but in order to succeed I had to apply the
> attached patch (#include <stdarg.h> from shlibs/blkid/src/blkidP.h).

The choice of shared library versions from util-linux-ng-2.16-rc2:
 	libblkid.so.1 -> libblkid.so.1.0.0
 	libuuid.so.1 -> libuuid.so.1.0.0
is somewhat unfortunate, because e2fsprogs-1.41.3 has:
 	libblkid.so.1 -> libblkid.so.1.0
 	libuuid.so.1 -> libuuid.so.1.2
with the consequence that as long as the older e2fsprogs libraries are not
removed, ldconfig will create a symlink to the older libuuid from e2fsprogs
(I am not sure about the symlink for libblkid).

This problem could safely be avoided if util-linux-ng were to choose at
least libuuid.so.1.2.0 or maybe even better to be absolutely safe
libblkid.so.1.1.0 and libuuid.so.1.3.0.

Regards
Peter
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ