Re: Chrooted packages, where to put them?
Stephen Frost <sfrost@ns.snowman.net> writes:
> If a library is shared between two
> packages and it can be modified by someone in one of the chroot'ed
> environments, that could affect the other chroot'ed environments.
The library is writable by root only, and the daemon does not run as
root. Or else, it could break out of the jail already.
> The way I compiled bind, IIRC, was to statically compile it so
> as to not have it depend on any libraries. Now, this does take it up
> from 452k to 1.8M, so I can see the desire to avoid that.
If you really want to give each daemon its own c-library (and the
daemon consists of only one or two binaries), it is more space-saving
to link statically. This way you only get the objects you need, rather
than the whole library, and the it is not PIC (which means: faster
and smaller on register-impaired archs like i386)
But as stated above, I don't think it gains you much.
--
Robbe
Reply to: