Re: a crude script to check shared library soname/package name integrity

[Ulrich Eckhardt <uli@doommachine.dyndns.org>]

On Friday 19 April 2002 01:06, Junichi Uekawa wrote:
> This line can be used to crudely check for suspicious
> soname/package name integrity, run it on your system, and
> see how much comes up :
>
>
> for A in /var/lib/dpkg/info/*.shlibs; do awk '$3 !~ $2"$" {print $0}' $A;
> done
>
A _lot_. However, what does this really check for ? And what are the 
conclusions you can draw from that ?
A few excerpts from what I get, can you comment on them?

libconsole 0 console-tools-libs (= 1:0.2.3-23.3)
libctutils 0 console-tools-libs (= 1:0.2.3-23.3)
libcom_err 2 libcomerr2, e2fsprogs (>= 1.27-2)
libss 2 libss2, e2fsprogs (>= 1.27-2)
libEterm 0.9.1 eterm
/usr/lib/libfakeroot/libfakeroot 0
libgif 3 libungif3g (>= 3.0-2) | giflib3g (>= 3.0-5.2)
libgdkcardimage 0 gnome-card-games
libkmultipage 0 kview (>= 4:2.2.2-0)
kword 0 kword
libdl   1       ldso (>= 1.9.7-0)
libbz2  0       libbz2
/lib/ld-linux 2 libc6 (>= 2.2.4-4)
ld-linux 2 libc6 (>= 2.2.4-4)
libdl 2 libc6 (>= 2.2.4-4)
libpam_misc 0 libpam0g (>= 0.72-1)
libpamc 0 libpam0g (>= 0.72-1)

thanks,
Ulrich Eckhardt


-- 
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org