Kevin F. Quinn (Gentoo) skrev:
On Fri, 12 May 2006 10:49:22 +0200
Simon Strandman <[EMAIL PROTECTED]> wrote:
I installed modular X on my server running hardened.
X on a server? If it's just for the libs that's ok, but running the X
server itself is risky on a server as it's huge and suid so flaws can
easily gain root access. One such was discovered just the other week
(http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-1526).
I have my reasons. I need to run VNC on it.
It was quite
annoying to have to switch back and forth betwen the vanilla gcc and
the hardened. I couldn't leave it on compiling over the night but had
to monitor it all the time. Is this really necessary? Why can't the
modular X eclass just append the appropriate CFLAGS/LDFLAGS that
disables bind now or whatever it is thar breaks X instead?
It could, if we had the time to get it working. It should work
passing '-nonow' to all invocations of gcc that do linking of relevant
bits, but for some reason when people have tried that it hasn't worked -
see bug #110506. We (hardened) haven't had the time to investigate
further, and we don't want to complicate the stabilisation effort of
modular X (which is a big enough job as it is) so we've left it as it
is for the moment. We'll probably start looking at it again once it
becomes stable (also upstream have a pending task to resolve the issue
properly, but don't hold your breath).
P.S. there's a hardened mailing list that is relevant.
Ok, thanks for the explanation! I'll keep track on that bug.
--
Simon Strandman - simon.strandman(a)telia.com
--
gentoo-dev@gentoo.org mailing list
