On Wed, Aug 13, 2008 at 10:22:26AM +0530, Suresh Jayaraman wrote:
> On a side note, another concern is that currently /sbin/cifs.spnego
> links quite a number of libraries present in /usr/lib. Allowing libs
> that are not inside root-fs for binaries in the root-fs is not a good
> libgssapi_krb5.so.2 => /usr/lib/libgssapi_krb5.so.2 (0xb7b6d000)
> libkrb5.so.3 => /usr/lib/libkrb5.so.3 (0xb7ad7000)
> libk5crypto.so.3 => /usr/lib/libk5crypto.so.3 (0xb7ab2000)
> libldap-2.4.so.2 => /usr/lib/libldap-2.4.so.2 (0xb7a6f000)
> liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0xb7a60000)
> libkrb5support.so.0 => /usr/lib/libkrb5support.so.0 (0xb7906000)
> libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0xb78ed000)
> libssl.so.0.9.8 => /usr/lib/libssl.so.0.9.8 (0xb78a8000)
> libcrypto.so.0.9.8 => /usr/lib/libcrypto.so.0.9.8 (0xb7764000)
> I'm not sure of a better way to handle this, though.
Is it at all plausible that users will need cifs.spnego to be present in
order to mount their /usr filesystem? If not, I don't see any reason the
binary should be in /sbin in the first place, and then linking libs from
/usr/lib isn't a problem. And indeed, most of these libraries are quite
relevant to the whole spnego upcall functionality...
This is different from mount.cifs, which needs to be in /sbin in order to be
found by the util-linux implementation of mount on Linux systems.
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer http://www.debian.org/