[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1453402008.3734.94.camel@decadent.org.uk>
Date: Thu, 21 Jan 2016 18:46:48 +0000
From: Ben Hutchings <ben@...adent.org.uk>
To: kernel-hardening@...ts.openwall.com
Cc: linux-kernel@...r.kernel.org
Subject: Re: [kernel-hardening] 2015 kernel CVEs
On Wed, 2016-01-20 at 10:04 -0800, Greg KH wrote:
> On Wed, Jan 20, 2016 at 05:05:39PM +0000, Ben Hutchings wrote:
> > On Tue, 2016-01-19 at 09:54 -0800, Greg KH wrote:
> > > On Tue, Jan 19, 2016 at 04:32:08PM +0000, Ben Hutchings wrote:
> > > > As for USB descriptors, I'm somewhat more hopeful about hardening. At
> > > > the same time, it seems like it should be practical to put more low-
> > > > performance USB drivers into userspace.
> > >
> > > What drivers do we currently have in the kernel that should/could be
> > > done in userspace instead? I'll gladly drop them from the tree.
> >
> > An obvious example would be HID drivers. (I'll grant you that putting
> > those in user-space would complicate the boot process when a disk
> > encryption passphrase is needed.)
>
> That and for userspace that expects to get an input device stream,
> combining serial, ps2, bluetooth, and USB devices all at the same time.
> So while it might be possible, keeping input devices and HID support in
> the kernel makes sense.
[...]
I was thinking that the HID drivers would feed events back into the
kernel through an enhanced version of evdev_write(). The userland
consumers of input events wouldn't need to change at all.
Ben.
--
Ben Hutchings
Horngren's Observation:
Among economists, the real world is often a special case.
Download attachment "signature.asc" of type "application/pgp-signature" (812 bytes)
Powered by blists - more mailing lists