From: Matthew Wilcox <matthew@wil.cx>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: Dave Airlie <airlied@gmail.com>,
peter.hutterer@who-t.net, linux-input@vger.kernel.org,
xorg@freedesktop.org
Subject: Re: Securing non-root X input
Date: Sun, 31 Jan 2010 10:08:01 -0700 [thread overview]
Message-ID: <20100131170801.GB1331@parisc-linux.org> (raw)
In-Reply-To: <20100131071307.GB12320@core.coreip.homeip.net>
On Sat, Jan 30, 2010 at 11:13:07PM -0800, Dmitry Torokhov wrote:
> > Yes, that's right. I didn't quite go far enough in my explanation
> > above ... the X server can look around the system to see what trusted
> > daemons (running as either root or the same user as the one running X)
> > currently have the device open, and notify the user if there's additional
> > openers that it isn't expecting.
>
> Then it will be constant race between X and the rest of the world with X
> pretty much always behind. Kind of like SELinux - as soon as try moving
> left or right the thing starts screaming at you...
Only if it's done badly (eg whitelisting HAL and Devkit). The algorithm
I proposed above (allow anything owned by root, and anything owned by
the same user that is running X) should be secure, and futureproof.
Ultimately, it's up to the distro to get this right.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2010-01-31 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 23:24 Securing non-root X input Matthew Wilcox
2010-01-30 7:45 ` Dmitry Torokhov
2010-01-31 1:35 ` Matthew Wilcox
2010-01-31 7:13 ` Dmitry Torokhov
2010-01-31 8:38 ` Dave Airlie
2010-01-31 8:50 ` Dmitry Torokhov
2010-01-31 17:08 ` Matthew Wilcox [this message]
2010-02-01 2:03 ` Dmitry Torokhov
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=20100131170801.GB1331@parisc-linux.org \
--to=matthew@wil.cx \
--cc=airlied@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=peter.hutterer@who-t.net \
--cc=xorg@freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.