mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Dave Airlie" <airlied@gmail.com>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: "linux-os (Dick Johnson)" <linux-os@analogic.com>,
	"Ed White" <ed.white@libero.it>,
	ML <linux-kernel@vger.kernel.org>
Subject: Re: SecurityFocus Article
Date: Fri, 12 May 2006 14:13:38 +1000	[thread overview]
Message-ID: <21d7e9970605112113s16764073tca5246d1e104503b@mail.gmail.com> (raw)
In-Reply-To: <9e4733910605112017u428c04cdm2ff40b53785db09c@mail.gmail.com>

>
> The X server doesn't need to go into the kernel, only a very tiny
> portion of it needs to go in. But X blindly pursues the idea of total
> platform independence which means it ignores many of the services
> offer by the Linux kernel and reimplements them in user space. This is
> because the BSDs are missing many things that Linux supports.
>
> I just love the idea of 2.4M lines of X code that opens network
> sockets needlessly running as root. Top it off with 1,300 unfixed
> Coverity hits, http://scan.coverity.com/. But what fun is life if you
> don't live a little dangerously. If you want ideas on how to fix X to
> not run as root read,
> http://people.freedesktop.org/~jonsmirl/graphics.html
>
> Of course DaveA will chime in and say that they are working on fixing
> things to use the Linux kernel. This is good and I am glad it is being
> done, I just worry that it will get finished sometime around 2014.

I'll also suggest you stop talking out of your arse, there are no
aliens in Area 51 either Jon and man did walk on the moon, refuting
the crap you post takes more time than fixing X...

Coverity scan is all of X (clients, libraries, server, apps) not just
the X server, it is also against the old 6.9 tree not the modular
tree, so it never gets anything fixed as that tree is dead. We are
working with coverity to scan modular instead.

My current X server hasn't any network sockets open by default.

Your ideas to fix X didn't result in patches to fix X, ideas are great
we all have ideas, patches are better, for some reason we don't all
have patches.

We are fixing X, you are not.

Dave.

  reply	other threads:[~2006-05-12  4:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 14:34 Ed White
2006-05-11 15:06 ` Andi Kleen
2006-05-11 15:32 ` Alan Cox
2006-05-11 15:47 ` linux-os (Dick Johnson)
2006-05-11 20:03   ` Ingo Oeser
2006-05-12  0:19   ` Segher Boessenkool
2006-05-12  3:17   ` Jon Smirl
2006-05-12  4:13     ` Dave Airlie [this message]
2006-05-12  5:07       ` Jon Smirl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21d7e9970605112113s16764073tca5246d1e104503b@mail.gmail.com \
    --to=airlied@gmail.com \
    --cc=ed.white@libero.it \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®