Re: Securing non-root X input

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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."
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux