Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [day] [month] [year] [list]
Date: Wed, 4 Jan 2017 14:59:12 -0600
From: Matthew Garrett <>
To: Greg KH <>
Cc: Petr Tesarik <>,, 
	Andrew Morton <>, Madalin Bucur <>,, Pavel Machek <>, 
	"Rafael J. Wysocki" <>, Ulf Hansson <>, 
	Rasmus Villemoes <>, Kees Cook <>, 
	Mauro Carvalho Chehab <>, Sudip Mukherjee <>, 
	Len Brown <>, Tomeu Vizoso <>, 
	Arnd Bergmann <>, Linux Kernel Mailing List <>, 
	Russell King <>, Lukas Wunner <>
Subject: Re: [PATCH] Allow userspace control of runtime disabling/enabling of
 driver probing

On Jan 4, 2017 12:47, "Greg Kroah-Hartman" <>

On Wed, Jan 04, 2017 at 02:01:00PM -0600, Matthew Garrett wrote:
> On Wed, Jan 4, 2017 at 1:47 PM, Greg Kroah-Hartman
> <> wrote:
> > You know the device type and vendor/product id before you authorize it,
> > you should be able to do this type of detection otherwise it seems
> > pretty pointless :)
> You know the vendor and product ID, which doesn't tell you whether one
> of the endpoints is a network device or a keyboard. You need to know
> that.

Are you sure you don't have the configuration information as well?  That
should tell you...

choose_config() isn't called until after authorisation, so even if scrape
that data you don't know what the kernel is going to choose.

And for network devices, they are almost all just vendor/product ids,
not many use the class protocol.

Plenty of stuff uses cdc.

Content of type "text/html" skipped

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.