Re: Help me fix a bug!
In an attempt to save the world from disaster, jdassen@wi.leidenuniv.nl wrote:
> On Sat, Mar 14, 1998 at 02:30:16PM +0100, Ole J. Tetlie wrote:
> > Peculiar indeed. Is there any reason for this? I can hardly see ldd as a
> > severe security hazard...
>
> See bug #13494 .
But other than that, ldd can be a "severe security hazard". That is
because ldd doesn't do anything itself, but it just executes ld.so
with a few environment varbiables set, so that ld.so "magically" starts
printing the used libraries.
So, when you see odd behaviour in ldd, it really is odd behaviour
in ld.so -- and ld.so can be a "severe security hazard".
(This is for David Engel's ld.so for libc5. The ld-linux that comes
with glibc2 (libc6) doesn't reqire environemnt variables, but
a command line option:
$ /lib/ld-linux.so.2 --list /bin/bash
libreadline.so.2 => /lib/libreadline.so.2 (0x40004000)
libncurses.so.3.4 => /lib/libncurses.so.3.4 (0x40026000)
libdl.so.2 => /lib/libdl.so.2 (0x4006b000)
libc.so.6 => /lib/libc.so.6 (0x4006e000)
/lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x00000000)
)
--
joost witteveen, joostje@debian.org
The upstream maintainer is allowed to do things different
than Debian, but only if he has good reasons to do so.
--
E-mail the word "unsubscribe" to debian-devel-request@lists.debian.org
TO UNSUBSCRIBE FROM THIS MAILING LIST. Trouble? E-mail to listmaster@lists.debian.org
Reply to: