"Erich Liebmann" <erich.liebm...@gmx.net> writes: > After trying 'ldd' with other binaries I am not sure whether, the fact > that only 'libc' is reported as a shared library dependency for 'scp' > and 'sftp-server', is related to VDSO, to the way the 'scp' and > 'sftp-server' binaries were created in the first place, or some other > factors.
I'm fairly sure that scp and sftp-server themselves just don't depend on any libraries other than libc and the dynamic loader. Checking a few different systems, they don't seem to. And there isn't any reason why they should need to; they don't do any cryptography. That's all done by the ssh binary. > Interestingly even 'readelf' reports only the 'libc' dependency for 'scp': > # readelf -d /usr/bin/scp | egrep NEEDED > 0x0000000000000001 (NEEDED) Shared library: [libc.so.6] > # That confirms that it definitely doesn't need other libraries. > I just know that on my old 'lenny' installation 'ldd' reported shared > library dependencies for 'scp' and 'sftp-server' corretly and > 'mkchroot.sh' created a working chroot environment. For some unkown > reason this does not seem to be the case any more on my new 'squeeze' > machine! What exactly doesn't work about the chroot environment? Maybe we're chasing the wrong thing. > I doubt that 'scp' depends only on 'libc', at least on my old 'lenny' > installation it had several other dependencies, including 'libcrypt' and > 'libnsl'. I suspect this was a cleanup of the build system. I don't think there are any fixes required to mkchroot, at least for those particular binaries. There's probably some fix required for *something* you're running into, but I think the ldd output is a red herring. If you could provide more information about what doesn't work in the chroot, that would be helpful in finding whatever the actual issue is. -- Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
